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
Implied essentiality levels of some @action values #184
Comments
charles is adding to escape fro clarification . see mintes for 24/5/2001 |
Currently we have the following in our list of values in section 3.1.4 of the Content Module 1
I propose the following for both cancel and escape
I am fine if we don't feel we also need to justify |
Just a quick note that we also discussed this on the group call: https://www.w3.org/2021/05/24-personalization-minutes.html |
Having re-read the minutes, I think we agreed to go with @clapierre's second option and revised wording. We also note @lseeman's point that we must be considering what's absolutely critical from the user's perspective. |
Just a further note that the discussion in the minutes seems to start at https://www.w3.org/2021/05/24-personalization-minutes.html#x103 |
Editorial change to close Issue #184
Close per Issue #194 |
I had some questions about the implied level of essentiality of some of the
action
attribute values:delete
isn't implicitly critical (but I expected it to be); do we know why? I know there is a note in the spec about the "delete" function being not necessarily essential for some tasks, so maybe that's why, but it seems quite context-dependant.escape
feels like it should be implicitly critical too, but isn't; do we know why?cancel
action too, which is marked as critical;cancel
is specified as relating entirely to dialogs. I wonder if it's a subset ofescape
?This maybe relates to (but is a separate/more specific question than) #66
The text was updated successfully, but these errors were encountered: