- From: <bugzilla@jessica.w3.org>
- Date: Mon, 16 Dec 2013 15:36:57 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24111 Frederico Caldeira Knabben <f.knabben@cksource.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX |--- --- Comment #2 from Frederico Caldeira Knabben <f.knabben@cksource.com> --- Thanks for the feedback, Robin. Unfortunately the :marker pseudo-element is not a solution for this as the root of the problem is that we don't know how to style the marker at CSS design time and in some instances (like the header sample in the reported fiddler), it is impossible even at CSS design time to do so (I mean, making the marker styled like a header). Since the very beginning I considered that this may not be a HTML issue, but I had mixed feelings when I saw the "Rendering" chapter at the HTML5 CR. On that chapter we have recommendations for rendering of lists, which in good part fit this proposal well. In fact, the proposal has nothing to do with adding features to HTML nor to CSS. It's all about rendering specs, specifying that :before and :after (and now :marker) pseudo-elements must inherit the styles of the source element contents. Then we understood that this would change the current rendering behavior out there, which is not good. So we proposed a CSS way to control whether to enable this new rendering way or not. So I still have a big question mark on where a rendering recommendation should land. I would appreciate if you could guide me on this. Meanwhile I'll start the same talk with the CSS WG. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 16 December 2013 15:37:02 UTC