Skip to content

[css-ui-4] Deal with locked editable elements and user-select #285 #2961

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[css-ui-4] Deal with locked editable elements and user-select #285 #2961

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion css-ui-4/Overview.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1541,6 +1541,11 @@ except:
where the computed value is always ''user-select/contain''
regardless of the specified value

<li>
on <a>locked editable element</a>s
where the computed value is ''user-select/contain''
if the specified value was ''user-select/text'' or ''user-select/auto''
Copy link
Member

@upsuper upsuper Jul 30, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as the handling of auto for this case is mentioned below, it can probably be removed here.


<li>
when the specified value is ''user-select/auto'',
which computes one of the other values as defined below
Expand All @@ -1551,6 +1556,10 @@ an <dfn>editable element</dfn> is either
an <a href="https://w3c.github.io/editing/contentEditable.html#dfn-editing-host">editing host</a>
or a <a href="https://www.w3.org/TR/html/sec-forms.html#mutable">mutable</a> form control with textual content,
such as <{textarea}>.
A <dfn>locked editable element</dfn> is
a normally <a href="https://www.w3.org/TR/html/sec-forms.html#mutable">mutable</a> form control with textual content,
when it is placed in a non mutable state,
such as a <{textarea}> with the <a href="https://html.spec.whatwg.org/multipage/input.html#the-readonly-attribute"><code>readonly</code></a> attribute.
Copy link
Member

@upsuper upsuper Jul 30, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems to me that this definition is probably not clear enough, for example, it is unclear whether a disabled form control is a "locked editable element". I guess the ambiguity is from "normally mutable form control". Is a disabled form control considered normally mutable? Or is being disabled just a non-mutable state?

Maybe explicitly referencing readonly attribute rather than listing it as an example may help? Something like "a otherwise mutable form control ... when it is placed in a non-mutable state by readonly attribute".


Issue: Should there be constraints
on what happens to the computed value
Expand All @@ -1570,7 +1579,7 @@ or maybe all values should compute to ''user-select/text''.
the computed value is ''user-select/none''

<li>
If the element is an <a>editable element</a>,
If the element is an <a>editable element</a> or a <a>locked editable element</a>,
the computed value is ''user-select/contain''

<li>
Expand Down