Yes, agree. 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 change but it seems that might not
be the case.
If not, we should send a Request for Position to figure out whether
there would be cross-browser alignment on shipping this.
-- Dan
*From:*Olli Pettay <opet...@mozilla.com>
*Sent:* Wednesday, May 22, 2024 9:53 AM
*To:* blink-dev <blink-dev@chromium.org>
*Cc:* Daniel Clark <dan...@microsoft.com>; Shuangshuang Zhou
<shuangshuang.z...@intel.com>
*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/LearnAboutSenderIdentification>
I think it is because of this rather surprising non-backwards
compatible 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 the WPTs at
https://wpt.fyi/results/selection/onselectionchange-on-distinct-text-controls.html
<https://wpt.fyi/results/selection/onselectionchange-on-distinct-text-controls.html>.
Can you help me understand the discrepancy there?
Thanks,
Dan
*From:*blin...@chromium.org <blin...@chromium.org> *On Behalf Of
*Shuangshuang Zhou
*Sent:* Tuesday, May 21, 2024 10:24 PM
*To:* blink-dev <blin...@chromium.org>
*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 important <https://aka.ms/LearnAboutSenderIdentification>
*Contact emails*shuangsh...@intel.com
*Explainer*None
*Specification*https://w3c.github.io/selection-api/#selectionchange-event
<https://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 latest specification of
selectionchange event. This also matches Safari behavior.
*Blink component*Blink>Editing>Selection
<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EEditing%3ESelection>
*TAG review*None
*TAG review status*Issues addressed
*Risks*
*Interoperability and Compatibility*
Interoperability risk is low because Firefox and Safari have
shipped this according to the specification. Compatibility risk is
low because the selectionchange event targeting input/textarea
would bubble up, and existing codes listening on Document will
work well as ever.
/Gecko/: Shipped/Shipping
/WebKit/: Shipped/Shipping (https://commits.webkit.org/276238@main
<https://commits.webkit.org/276238@main>)
/Web developers/: No signals
/Other signals/:
*WebView application risks*
/Does this intent deprecate or change behavior of existing APIs,
such that it has potentially high risk for Android WebView-based
applications?/
Low WebView application risks.
*Debuggability*
None
*Will this feature be supported on all six Blink platforms
(Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?*Yes
*Is this feature fully tested by **web-platform-tests*
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>*?*Yes
https://wpt.fyi/results/selection/onselectionchange-on-distinct-text-controls.html
<https://wpt.fyi/results/selection/onselectionchange-on-distinct-text-controls.html>
*Flag name on chrome://flags*None
*Finch feature name*DispatchSelectionchangeEventPerElement
*Requires code in //chrome?*False
*Tracking bug*https://issues.chromium.org/issues/330766600
<https://issues.chromium.org/issues/330766600>
*Estimated milestones*
Shipping on desktop
127
*Anticipated spec changes*
/Open questions about a feature may be a source of future web
compat or interop issues. Please list open issues (e.g. links to
known github issues in the project for the feature specification)
whose resolution may introduce web compat/interop risk (e.g.,
changing to naming or structure of the API in a
non-backward-compatible way)./
None
*Link to entry on the Chrome Platform
Status*https://chromestatus.com/feature/5255454895898624?gate=6043023317401600
<https://chromestatus.com/feature/5255454895898624?gate=6043023317401600>
This intent message was generated by Chrome Platform Status
<https://chromestatus.com/>.
--
You received this message because you are subscribed to the Google
Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/de18f3c4-df5a-4423-80ec-e505e0c9fb2bn%40chromium.org
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/de18f3c4-df5a-4423-80ec-e505e0c9fb2bn%40chromium.org?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google
Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/PH8PR00MB1445785C11C8FCA346EAE963C5EB2%40PH8PR00MB1445.namprd00.prod.outlook.com
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/PH8PR00MB1445785C11C8FCA346EAE963C5EB2%40PH8PR00MB1445.namprd00.prod.outlook.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/51bafc9e-379f-4320-bc7e-53b918921a90%40chromium.org.
