From: MarLinn <monkleyon-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Should the HTML writer generate empty '<span>' elements?
Date: Sun, 5 Sep 2021 00:49:33 +0200 [thread overview]
Message-ID: <543ae04c-c5ef-99c3-cff7-15068893b3e4@gmail.com> (raw)
In-Reply-To: <CAMwO0gywhE+u4wgaL0sieohjuqAm+VM2Lj489EsQST74FMqrMA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]
Possible use cases for an empty span that I can think of off the top of
my hat:
* Clearfix
* As a placeholder that will be filled/replaced by javascript
* As a placeholder that will be filled/replaced by a pandoc filter
* As an anchor for before/after pseudoelements
* As a container for a background-image
* As a piece in some CSS trickery to get fancy effects without images
* To have the right count of elements for some table-like presentation
* Because of symmetry with some other structure where there is content
inside the span
There's probably a lot more, these are just some cases I thought of. Is
an empty span always the /best/ solution to these problems? Probably
not. But sometimes it is.
The most relevant as it relates to pandoc is probably the third one: in
a pandoc filter. Because of that I would not want to see this feature be
removed.
Now, should the span be self-closing? That's a different question. I
suspect that /that's/ the main reason for many/all of the errors you're
seeing, not the pure empty-ness. So that might be something worth
changing. But as you're saying, that's a Hakyll problem, not a Pandoc
problem.
Cheers.
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/543ae04c-c5ef-99c3-cff7-15068893b3e4%40gmail.com.
[-- Attachment #2: Type: text/html, Size: 2344 bytes --]
next prev parent reply other threads:[~2021-09-04 22:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 16:08 Gwern Branwen
[not found] ` <CAMwO0gywhE+u4wgaL0sieohjuqAm+VM2Lj489EsQST74FMqrMA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-09-04 22:49 ` MarLinn [this message]
[not found] ` <543ae04c-c5ef-99c3-cff7-15068893b3e4-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-09-04 23:15 ` Gwern Branwen
[not found] ` <CAMwO0gyKnt3aaaGqM_D61ttQOM0v4iz2uHM3RtW9pgkiO+fWXg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-09-05 0:51 ` MarLinn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=543ae04c-c5ef-99c3-cff7-15068893b3e4@gmail.com \
--to=monkleyon-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).