- From: <bugzilla@jessica.w3.org>
- Date: Tue, 10 Mar 2015 02:26:52 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28170 Tab Atkins Jr. <jackalmage@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #13 from Tab Atkins Jr. <jackalmage@gmail.com> --- (In reply to Andrea Rendine from comment #12) > This does make sense somehow. A slow rendering means FOUC on heavy pages, so > it's better to have something easy. > Just hope to see it fully specified and implemented soon. > > One final request before this bug is closed: will the new display- rendering > rule allow <br> and <wbr> to be styled differently? I mean, the spec > explicitly says that an author could design a page so that <br> are rendered > as "green dots", another could use <wbr> to represent (soft)hyphenated > string- or word-break. Will display-outside behavior allow for such a design? > > Thanks for the piece of info about vendors. It's the point I had missed. Yup, once you switch your rendering over to looking at the 'display' value rather than checking tagname, that means that if the author sets it to some *other* 'display' value, it'll render as a normal (empty) element with that 'display'. I guess I'll go ahead and close this, then. ^_^ -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 10 March 2015 02:26:59 UTC