Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[css-ui-4] controlling selection for list decorators? #284

Open
reschke opened this issue Jul 7, 2016 · 5 comments
Open

[css-ui-4] controlling selection for list decorators? #284

reschke opened this issue Jul 7, 2016 · 5 comments
Assignees
Labels
css-ui-4 Current Work

Comments

@reschke
Copy link

reschke commented Jul 7, 2016

https://drafts.csswg.org/css-ui-4/#content-selection

It would be good if it was possible to control selection for autogenerated list decorators (such as item numbers in an ordered list). That would make copying lists out of the browser into plain text messages less painful.

@frivoal frivoal added the css-ui-4 Current Work label Jul 8, 2016
@frivoal
Copy link
Collaborator

frivoal commented Jul 8, 2016

This is related to the question of selectabilty of the ::before and ::after pseudo elements.
One approach would be to say that ::marker { user-select: none; } means they cannot be selected, while ::marker {user-select: text; } means they can.

This still leaves (just as it does for ::before and ::after) some questions open:

  • What should be the default? Historical precedent suggests it should be none or something (auto?) that computes to none. Do we solve that via auto computing to none, or via UA stylesheets having ::marker { user-select: none; } But it isn't even clear that the historical default is actually the desired behavior.
  • Is this synchronized with copy and paste? Selection related APIs? Accessibility views? Hopefully the answer would be yes, but it isn't clear that the APIs concerned are in sync with eachother, or capable of dealing with stuff that's not in the DOM. Here the answer may be different between ::marker on the one hand and ::before and ::after on the other. Or maybe not.

@frivoal frivoal self-assigned this Jul 8, 2016
@frivoal
Copy link
Collaborator

frivoal commented Jul 8, 2016

(Note: the concerned raised in this issue is reflected in https://drafts.csswg.org/css-ui-4/#issue-9901bc8c in the spec, while the extra questions I raised are in https://drafts.csswg.org/css-ui-4/#issue-1a7baa20)

@frivoal
Copy link
Collaborator

frivoal commented Jul 8, 2016

The editing TF part of this discussion is there: http://www.w3.org/mid/04c3339e-c1d9-25d3-8f4f-e40659ed4db8@gmx.de

@reschke
Copy link
Author

reschke commented Jul 8, 2016

Thanks for tracking this. FWIW, I agree that the current default might actually not what people want.

@frivoal frivoal changed the title [css-ui] controlling selection for list decorators? [css-ui-4] controlling selection for list decorators? Apr 24, 2017
@frivoal
Copy link
Collaborator

frivoal commented Nov 3, 2017

@astearns @atanassov I think we cannot close this one without getting some input from other WGs, to figure out how this would work from the point of view of DOM centric APIs relating to selectability etc. Could we use TPAC to try and get some other people in the room and talk through this? I'll tentatively add this to the agenda in the hope we can.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
css-ui-4 Current Work
Projects
None yet
Development

No branches or pull requests

3 participants