Oh, I forgot to ask a11y team, sorry.
On 11/21/2025 11:58 AM, 'James Teh' via [email protected] wrote:
On Fri, Nov 21, 2025 at 12:39 PM Masayuki Nakano
<[email protected]> wrote:
Instead, the layout module stops painting non-selectable content
as selected by itself.
Does this include content marked with CSS user-select: none?
Yes, it does. Previously, they were not contained into the selection
ranges by a user's operation, but were contained into them if the range
is added by JS. Previously, the layout module does not consider whether
painting selection highlight by itself. However, now, each frame checks
whether the frame is selectable or not to stop painting as selected.
When accessibility clients (like screen readers) select a range of
text, they don't necessarily know that there is non-selectable content
in the middle, so they just select the entire range. Because of this,
we apparently have a bug in Firefox where if you select a range of
text with VoiceOver and that range contains non-selectable content,
the visually painted selection includes the non-selectable content
<https://github.com/w3c/css-aam/issues/7#issuecomment-3537024255:~:text=Although%20in%20Firefox%20142%20the%20selection%20box%20was%20drawn%20over%20the%20user%2Dselect%3A%20none%20element%20when%20using%20the%20VoiceOver%20text%20selection%20command%20%28VO%2BReturn%29%2E>,
even though it isn't copied to the clipboard. I'm wondering whether
this change will "fix" this bug.
Oh, sounds nice. That should be fixed by the patches in the next Nightly
build.
--
Masayuki Nakano<[email protected]>
Working on DOM, Events, editor and IME handling for Gecko
--
You received this message because you are subscribed to the Google Groups
"[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/3797538d-136f-4a48-8be8-2e4f36e2085b%40d-toybox.com.
