[Bug 28170] Reference to CSS element content in <br> and <wbr> rendering

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28170

--- Comment #8 from Tab Atkins Jr. <jackalmage@gmail.com> ---
(In reply to Andrea Rendine from comment #7)
> I see. Yes, I found an IRC log from Feb 23 where you wrote the same. Is that
> true that display-outside is not supported by browsers yet, not even in for
> other values? And that <br> and <wbr> elements would be the only uses for
> display-outside values "newline" and "break-opportunity" respectively?

Yes.  It's fine for specs to normatively describe behavior in terms of
properties that aren't implemented yet; the browsers will match when they
implement the behavior.

And yes, these are the only consumers of those values; the values are being
added *for the purpose of describing these elements*.  Right now they're
"magic" and do things that are impossible to describe with current styles.  (Or
at least, difficult to describe, and sufficiently expensive that browsers won't
implement them in the existing terms due to the ubiquity of the elements on the
web.)

> Anyway, apart from my previous reply, this doesn't apply to W3 HTML5.1
> working draft, which still shows the old rendering rule (maybe it's just a
> matter of not being updated since last July). The problem is, both the
> display-outside and the element{content} are now impractical solutions, i.e.
> solutions based on currently un-standardized and unsupported CSS properties.
> On the contrary, as I noticed above, a simple element::after{content} seems
> a base to solve the issue, using standard, supported rules. Is there a
> reason why this hasn't been proposed? (It's just a layman's
> request/idea/proposal)

That only works for <br>, and we can't do it because it's possible today to
have a "br::after {...}" rule in your page, and making <br> rely on that
selector would break such pages.  Also, as I alluded to above, the use of
'content'/etc is actually rather slow and unoptimized; that's fine when you're
doing it for a handful of things in your page, but not as acceptable for
browsers to use for every <br>.

It doesn't work for <wbr> at all.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 9 March 2015 22:02:05 UTC