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

It seems that I misunderstood Florian's message. Sorry about that.

Since Tab does represent Google, I sincerely hope that he briefly
illustrate the technical reason that Google regards ::wrap as hard to
implement.

However, Google does not represent Mozilla. What Google regards as hard is
not necessarily be hard to Mozilla. So universal references are still
needed in order to show that all implementors regard ::wrap as hard to
implement.

2016-10-19 10:28 GMT+08:00 Ian Yang <ian.html@gmail.com>:

> Thanks Florian Rivoal. Could you please let us know of which browser you
> are currently an implementor, and the technical reason that you regard
> ::wrap as hard to implement?
>
> 2016-10-19 10:20 GMT+08:00 Florian Rivoal <florian@rivoal.net>:
>
>>
>> On Oct 19, 2016, at 10:25, Ian Yang <ian.html@gmail.com> wrote:
>>
>> 2016-10-18 20:17 GMT+08:00 Sebastian Zartner <sebastianzartner@gmail.com>
>> :
>>
>>> On 18 October 2016 at 09:42, Ian Yang <ian.html@gmail.com> wrote:
>>> >
>>> > 2016-10-11 11:37 GMT+08:00 Ian Yang <ian.html@gmail.com>:
>>> >>
>>> >> For your information, an issue had just been opened in W3C's CSSWG
>>> repository for editor's drafts on GitHub. The url is
>>> https://github.com/w3c/csswg-drafts/issues/588
>>> >>
>>> >> Your participation is welcomed.
>>> >
>>> >
>>> > Maybe I wasn't made it clear that the purpose of the thread is to get
>>> more people involved when I was creating the thread on GitHub. Therefore
>>> there had been no one replied after a week. And after I post a reply an
>>> hour ago to encourage people to participate, soon there was someone replied.
>>> >
>>> > So if you are willing to see this pseudo element being added and CSS
>>> become more superior, please kindly participate. Thank you very much.
>>>
>>> I've added some more comments on the GitHub issue. I suggest to
>>> continue the discussion there.
>>>
>>> Sebastian
>>>
>>
>> It looks like that the thread on GitHub has been closed by Mr. Tab
>> Atkins Jr., and the reason is that implementors have historically been
>> strongly against this sort of functionality.
>>
>> However, ever since the the topics were created at here and on GitHub, we
>> haven't seen a single implementor say this feature is very hard to
>> implement. I hope Tab Atkins can provide us with some references or evidences
>> that prove implementors' anti-interest.
>>
>>
>> Tab does represent Google, so I would count his voice has one implementor.
>>
>>  - Florian
>>
>>
>