gt;>>> Hopefully it doesn't break any real web sites.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi Dan, I think we could submit a standard-position issue
>>>>>>>>>>> to Mozilla for reducing duplicated events i
> soon, next week at latest. So hopefully we'll get feedback if it
>>>>>>>>> breaks
>>>>>>>>> something.
>>>>>>>>> I don't think there is need for a standards-position for this
>>>>>>>>
for this
>>>>>>>> particular small tweak.
>>>>>>>> (But the process of making this kind of breaking spec change was
>>>>>>>> rather unusual.)
>>>>>>>>
>>>>>>>>
>>>&g
ling the
>>>>>>>> WPTs at
>>>>>>>> https://wpt.fyi/results/selection/onselectionchange-on-distinct-text-controls.html,
>>>>>>>>
>>>>>>>> that might be another issue. Let me make more explanation.
>>>>
> Since Gecko already implements the behavior of firing
>>>>>>> selectionchange on input/textarea (confirmed here
>>>>>>> <https://glow-curvy-cerise.glitch.me/>), sounds good to me to go
>>>>>>> ahead with shipping this change in Ch
tarea for
>>>>>> the
>>>>>> first step. Then the second CL in WebKit is 276388@main
>>>>>> <https://commits.webkit.org/276388@main>, which finally avoided to
>>>>>> fire duplicated selectionchange events according to th
>>>>> Separately, for the behavior of not firing duplicate selectionchange,
>>>>> it might not hurt to go ahead and request an official Mozilla position on
>>>>> that since it sounds like there’s still a bit of uncertainty about landing
>>>
xt-controls.html, chrome and firefox
>>>> should
>>>> be failed because only Safari has landed 2 CLs to avoid duplicated
>>>> selectionchange events. Or in other words, firefox might already dispatch
>>>> selectionchange event on elements but doesn'
d to
>>> fire scheduled-but-not-executed events.
>>>
>>>
>>>
>>> For WebKit, currently the two CLs are both landed in Safari Technology
>>> Preview 192(link
>>> <https://developer.apple.com/documentation/safari-technology-preview-re
*Sent:* Friday, May 24, 2024 12:26 AM
>> *To:* blink-dev
>> *Cc:* Shuangshuang Zhou ; tk...@chromium.org <
>> tk...@chromium.org>; mike...@chromium.org ; Daniel
>> Clark ; Olli Pettay
>> *Subject:* Re: [blink-dev] Intent to Ship: Dispatch selectionchange
&
ree. Can we please request a position from Mozilla at
> https://github.com/mozilla/standards-positions/issues/new?
>
> On 5/22/24 6:43 PM, 'Daniel Clark' via blink-dev wrote:
>
> Yeah, that’s what I was trying to get at – the Intent implies that Gecko
> has also shipped the breaking c
; mike...@chromium.org ; Daniel
Clark ; Olli Pettay
Subject: Re: [blink-dev] Intent to Ship: Dispatch selectionchange event per
element
You don't often get email from opet...@mozilla.com<mailto:opet...@mozilla.com>.
Learn why this is important<https://aka.ms/LearnAboutSenderIdentifica
s-positions/issues/new?
>>>> On 5/22/24 6:43 PM, 'Daniel Clark' via blink-dev wrote:
>>>>
>>>> Yeah, that’s what I was trying to get at – the Intent implies that
>>>> Gecko has also shipped the breaking change but it seems that might not be
&g
; recent change.
>>>
>>> On Wednesday, May 22, 2024 at 7:28:45 PM UTC+3 Daniel Clark wrote:
>>>
>>> The Gecko status is marked as Shipped/Shipping and the Interop/Compat
>>> section mentions Firefox having shipped this, but Firefox is still failing
>&
end a Request for Position to figure out whether there
>> would be cross-browser alignment on shipping this.
>>
>>
>>
>> -- Dan
>>
>>
>>
>> *From:* Olli Pettay
>> *Sent:* Wednesday, May 22, 2024 9:53 AM
>> *To:* blink-dev
>&
ing this.
>
>
>
> -- Dan
>
>
>
> *From:* Olli Pettay
> *Sent:* Wednesday, May 22, 2024 9:53 AM
> *To:* blink-dev
> *Cc:* Daniel Clark ; Shuangshuang Zhou
>
> *Subject:* Re: [blink-dev] Intent to Ship: Dispatch selectionchange event
> per element
:* Re: [blink-dev] Intent to Ship: Dispatch selectionchange
event per element
You don't often get email from opet...@mozilla.com
<mailto:opet...@mozilla.com>. Learn why this is important
<https://aka.ms/LearnAboutSenderIdentification>
I think it is because of
Pettay
Sent: Wednesday, May 22, 2024 9:53 AM
To: blink-dev
Cc: Daniel Clark ; Shuangshuang Zhou
Subject: Re: [blink-dev] Intent to Ship: Dispatch selectionchange event per
element
You don't often get email from opet...@mozilla.com<mailto:opet...@mozilla.com>.
Learn why this is imp
> *Shuangshuang
> Zhou
> *Sent:* Tuesday, May 21, 2024 10:24 PM
> *To:* blink-dev
> *Subject:* [blink-dev] Intent to Ship: Dispatch selectionchange event per
> element
>
>
>
> You don't often get email from shuangsh...@intel.com. Learn why this is
> im
there?
Thanks,
Dan
From: blink-dev@chromium.org On Behalf Of Shuangshuang
Zhou
Sent: Tuesday, May 21, 2024 10:24 PM
To: blink-dev
Subject: [blink-dev] Intent to Ship: Dispatch selectionchange event per element
You don't often get email from
shuangshuang.z...@intel.com<mailto:shuangshuang.z...@intel.
Contact emailsshuangshuang.z...@intel.com
ExplainerNone
Specificationhttps://w3c.github.io/selection-api/#selectionchange-event
Summary
Dispatches selectionchange event per element when this
element(input/textarea) provides a text selection or its selection changes.
This is to match the
22 matches
Mail list logo
