Re: [csswg-drafts] [css-pseudo-4] ::selection vs ::inactive-selection (#4579)

The CSS Working Group just discussed `[css-pseudo-4] ::selection vs ::inactive-selection`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-pseudo-4] ::selection vs ::inactive-selection<br>
&lt;dael> github:<br>
&lt;dael> fantasai: Looked like going to use pseudo class combo but I didn't have anything to move forward with what it would be. Some comments on window for active but selection can be inactive when window is active. I'm not sure all behaviors intended or if we can do it all. I need help figuring it out. Does anyone have enough familiarity to know where we need the switch?<br>
&lt;dael> AmeliaBR: Browsers must have this code b/c they have default highlight styles. I guess it's a question to dig into code bases and look for consistency we can build on<br>
&lt;dael> emilio: Somewhat familiar with Gecko. Inactive selections in active window just not rendered. An input an have selection-start and -end but if you select outside we don't render selection on input<br>
&lt;dael> fantasai: Selected but invisible?<br>
&lt;dael> emilio: Yes<br>
&lt;dael> florian: Feels like different things<br>
&lt;dael> fantasai: Than it is selected, right? Maybe that's another state. It's selected and selection has default background<br>
&lt;dael> emilio: Opposite. Two states, window-active and -inactive. I think confusing to users if you allow display selection of something they can't edit b/c not focusable<br>
&lt;dael> emilio: afaict in FF there's active and inactive selection and that's it. Inactive matches the inactive window<br>
&lt;dael> fantasai: Active selection in active window, selection in inactive window, invisible selection?<br>
&lt;dael> emilio: Active selection in do that's main or not and that's only when they are active and rendered.<br>
&lt;dael> fantasai: I'm playing with it so I can see it.<br>
&lt;dael> fantasai: Question on what other browsers do.<br>
&lt;dael> fantasai: Also, can you from the DOM tell if content in the invisible input selection is selected?<br>
&lt;dael> emilio: I think so from DOM APIs. Only want to access is selection-start and -end. This is from memory<br>
&lt;dael> florian: Actually selected? If you copy do you copy from it?<br>
&lt;dael> emilio: ONly from active section of active window<br>
&lt;dael> florian: Feels like it could not be a selection<br>
&lt;dael> emilio: If you programmatically focus you should it<br>
&lt;dael> florian: It's a memory of where selction would be created if you focus the element<br>
&lt;dael> florian: If you do operations it acts on that selection?<br>
&lt;dael> emilio: I don't think so<br>
&lt;AmeliaBR> q?<br>
&lt;dael> fantasai: florian concept makes snese but how is it in the DOM? THer'es active, inactive, and remembered selection.<br>
&lt;dael> emilio: ALso things like defining page 1 which is different states. Don't know if we want to expose to authors<br>
&lt;dael> fantasai: Still need info on blink and webkit<br>
&lt;dael> AmeliaBR: Quick test. Chromium on windows is same as FF in that it remembers selections in imputs but no style if move focus away<br>
&lt;dael> AmeliaBR: One difference is if you have selection inside iframe and tab away FF it's same as inactive window selection, chromium no highlighting except regular input<br>
&lt;dael> AmeliaBR: Both have the style where inactive window gets different style effect<br>
&lt;dael> AmeliaBR: If point is represent browser default in CSS having inactive in combo with selection is sufficient. Can't check webkit, but chromium and FF that's the main requirement<br>
&lt;dael> fantasai: Good to hear from webkit. In terms of window active vs not I think that's a MQ not pseudo class<br>
&lt;dael> astearns: Sounds like we need test cases to outline scenarios and see if there's concordance between browsers and than decide how we'll express<br>
&lt;dael> fantasai: Seems like we could replecate what we know of with active window MQ and ::Selection and need to know if works on webkit.<br>
&lt;dael> smfr: Get webkit data for next week<br>
&lt;dael> fantasai: Okay<br>
&lt;dael> fantasai: Current state of proposal is we propose no active vs inactive media query [missed] Any comment on that approach assuming it checks out?<br>
&lt;dael> astearns: We'll leave this open. Keep on the agenda or wait on data?<br>
&lt;dael> fantasai: Wait on webkit<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at using your GitHub account

Received on Wednesday, 27 May 2020 16:36:07 UTC