W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2016

[csswg-drafts] [css3-selector]: Proposal: Adop ::wrap pseudo element

From: Ian Yang via GitHub <sysbot+gh@w3.org>
Date: Tue, 11 Oct 2016 03:34:30 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-182165632-1476156868-sysbot+gh@w3.org>
Ian-Y has just created a new issue for 
https://github.com/w3c/csswg-drafts:

== [css3-selector]: Proposal: Adop ::wrap pseudo element ==
Please find the information of `::wrap` pseudo element through [this 
hyperlink](https://wiki.csswg.org/ideas/pseudo-elements#complex-wrapping-of-selector-range).

There are abundant use cases of this pseudo element. For example, 
because there has been no wrapper element for wrapping `<dt>` and 
`<dd>` pairs in description list `<dl>`, web developers have been 
having no choice but to resort to JavaScript to insert `<li 
role="presentation"></li>` into `<dl>` or even use less semantic list 
element like `<ul>`. Yet another example is that, layout designs such 
as "left and right columns" is everywhere so we have been having to 
add extra wrapper `<div>`s into HTML for that kind of purpose.

The aforementioned examples are just a tip of iceberg. The use cases 
of `::wrap` are a lot more than the use cases of `:first-child`, 
`:empty`, etc.

Could we please have the aforementioned `::wrap` pseudo element be 
formally adopted? With this pseudo element, web developers would be 
able to write more semantic HTML and no longer have to resort to 
JavaScript, which results in the unwanted 
[FOUC](https://en.wikipedia.org/wiki/Flash_of_unstyled_content). From 
the aspect of use case, there seems to be no reason why this pseudo 
element should not be adopted.


Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/588 using your GitHub 
account
Received on Tuesday, 11 October 2016 03:34:37 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:04 UTC