W3C home > Mailing lists > Public > www-style@w3.org > October 2016

Re: [css3-selectors]: Proposal: Adop the ::wrap pseudo element

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 6 Oct 2016 14:43:01 -0700
Message-ID: <CAAWBYDCr7wzxjEy10uLk-MjkEnHFZmx92ke9q124eY6EF06sQQ@mail.gmail.com>
To: Marat Tanalin <mtanalin@yandex.ru>
Cc: Ian Yang <ian.html@gmail.com>, CSS public list <www-style@w3.org>
On Thu, Oct 6, 2016 at 1:53 PM, Marat Tanalin <mtanalin@yandex.ru> wrote:
> 06.10.2016, 23:25, "Tab Atkins Jr." <jackalmage@gmail.com>:
>> On Thu, Oct 6, 2016 at 1:45 AM, Ian Yang <ian.html@gmail.com> wrote:
>>>  This pseudo element can do a lot more than just wrapping <dt> and <dd>
>>>  pairs. For years, we have been adding extra <div>s or <span>s into our HTML
>>>  codes just because we have to achieve a certain layout or positioning. With
>>>  ::wrap pseudo element, we can say good bye to that inflexible approach and
>>>  styling or redesigning web pages would become impressively flexible and
>>>  time-saving.
>> To be clear, we only add features to the spec that have use cases and
>> interest in being implemented in at least two major browser engines.
> There is also an opposite thing: some browser vendors are not willing to implement features _until_ they are standardized. So we have a sort of closed circle here.

Most incentive structures are indeed somewhat circular, yes.

But this circle isn't vicious.  "Not interested until standardized" is
almost always actually "not willing to publicly commit while it's
still an amorphous idea".  This is one of the many reasons we're
trying to shift things to incubation-first - it encourages grabbing
implementor interest early, lets less-committed implementors come in
later, and does it all without requiring the group to give the Stamp
Of Approval that putting something in a draft does.

Received on Thursday, 6 October 2016 21:43:51 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:15:01 UTC