Re: [gnus git] branch master updated: =1= shr.el (shr-tag-div): Added.

[Katsumi Yamaoka <yamaoka@jpl.org>]

Lars Magne Ingebrigtsen wrote:
> Yeah, that's bad, but stuff like

> This is a sentence with <div style="inline; color: blue;">blue</div>
> text from someone who doesn't know about span.

> will be rendered as

> This is a sentence with
> blue
> text from someone who doesn't know about span.

> instead of

> This is a sentence with blue text from someone who doesn't know about
> span.

Oh, that's too bad.  I only know that many web pages describe like
this:

Browsers usually place a line break before and after the div element.

(This example is from: http://www.w3schools.com/tags/tag_div.asp)

> I'm not sure what's worse, or what's more common.  Just leave it as is
> now (with the ensure-newline stuff), and we'll see how things look...

> Of course, we could start parsing the CSS, but then we'd have to have
> something else that shr could stand for, because it wouldn't be "Simple
> HTML Renderer" any more.  :-)

Agreed. ;-)

> I took a stab at it for "color" in span, but I'm not particularly
> satisfied with the result.  That is, somebody has <span color="blue">,
> which renders the text totally unreadable for me, because I use a black
> background.  So I was thinking about either backing that out again
> or...  er...  well, I don't have an "or".  :-)