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

Implied essentiality levels of some @action values #184

Closed
matatk opened this issue Apr 26, 2021 · 6 comments
Closed

Implied essentiality levels of some @action values #184

matatk opened this issue Apr 26, 2021 · 6 comments
Assignees

Comments

@matatk
Copy link
Contributor

matatk commented Apr 26, 2021

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?
    • I note we have a cancel action too, which is marked as critical; cancel is specified as relating entirely to dialogs. I wonder if it's a subset of escape?

This maybe relates to (but is a separate/more specific question than) #66

@lseeman
Copy link
Contributor

lseeman commented May 24, 2021

charles is adding to escape fro clarification . see mintes for 24/5/2001
other issues are agreeed

@clapierre
Copy link
Contributor

Currently we have the following in our list of values in section 3.1.4 of the Content Module 1

cancel Closes the dialog and discards any changes the user may have made within that dialog. (Implied simplification = "critical".)
escape Typically used to abort, cancel or change what is currently being displayed on the screen. A common application of the the esc key is to leave full screen mode.

I propose the following for both cancel and escape

cancel Closes the dialog and discards any changes the user may have made within that dialog. (Implied simplification = "critical", the reason being if there is no escape option cancel must be present to abort the operation)
escape Typically used to abort, cancel or change what is currently being displayed on the screen. A common application of the the esc key is to leave full screen mode. (implied simplification = "critical", the reason being if there is no cancel option escape must be present to abort the operation)

I am fine if we don't feel we also need to justify cancel as requiring critical simplification and leave its definition alone and only update escape.

@matatk
Copy link
Contributor Author

matatk commented Jul 31, 2021

Just a quick note that we also discussed this on the group call: https://www.w3.org/2021/05/24-personalization-minutes.html

@matatk
Copy link
Contributor Author

matatk commented Aug 2, 2021

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.

@matatk
Copy link
Contributor Author

matatk commented Aug 2, 2021

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

@johnfoliot johnfoliot self-assigned this Aug 9, 2021
johnfoliot added a commit that referenced this issue Aug 9, 2021
Editorial change to close Issue #184
@johnfoliot
Copy link
Contributor

Close per Issue #194

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants