From: "T.V Raman" <raman@google.com>
To: theophilusx@gmail.com
Cc: larsi@gnus.org, raman@google.com, emacs-devel@gnu.org
Subject: Re: EWW: Render span tags with spaces aroun them?
Date: Fri, 16 Oct 2020 07:45:14 -0700 [thread overview]
Message-ID: <24457.45562.533096.553682@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <CAC=50j_Oys2yTpfLgkjFQTWELD6zcNMHSo1uWZur+9+Cr89dnw@mail.gmail.com>
Thanks for looking Tim, hopefully you speak enough cricket to spot the
bug.
Cricinfo shows live scores during IPL games, when games are live,
player names are running into the player's runs scored. In the markup,
there an empty <comment></comment> element that may well be getting
styled via css (comment as far as I know is not part of html)Tim Cross writes:
> I agree. Adding spaces for span elements will change the semantics and
> likely affect other rendering in a negative way. For example, sometimes you
> may use span to style just part of some text or it could affect layout of
> things like icons etc. I note that neither chrome or firefox add spaces and
> will just run the text into the previous/next word if there is no space
> around the tag.
>
> Having said that, I notice when looking at the example page you posted,
> there is no text running into previous/next text around span tags. This
> makes me think that the page is using a CSS style to style the element
> which is not honoured by eww/shr? I had a quick look, but it really is a
> very ugly piece of HTML. At any rate, perhaps the issue is not that span
> elements should have spaces added, but that eww/shr is not able to add the
> CSS style which adds the spacing to the span content?
>
> On Fri, 16 Oct 2020 at 15:54, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> > "T.V Raman" <raman@google.com> writes:
> >
> > > But the user visible breakage is that things get run together and the
> > > easiest fix might be to ensure that span tags when rendered are
> > > surrounded by spaces
> >
> > The <span> rendering shouldn't have any extra spaces -- that's not what
> > the element was designed for, and will make many texts unreadable.
> >
> > --
> > (domestic pets only, the antidote for overdose, milk.)
> > bloggy blog: http://lars.ingebrigtsen.no
> >
> >
>
> --
> regards,
>
> Tim
>
> --
> Tim Cross
--
♉Id: kg:/m/0285kf1 🦮♉
--
♉Id: kg:/m/0285kf1 🦮♉
prev parent reply other threads:[~2020-10-16 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 17:13 EWW: Render span tags with spaces aroun them? T.V Raman
2020-10-16 4:52 ` Lars Ingebrigtsen
2020-10-16 5:57 ` Tim Cross
2020-10-16 6:25 ` Lars Ingebrigtsen
2020-10-16 14:45 ` T.V Raman [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=24457.45562.533096.553682@retriever.mtv.corp.google.com \
--to=raman@google.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=theophilusx@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).