-
Notifications
You must be signed in to change notification settings - Fork 60
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
Redundant Media Overlays escapability normative statements #2284
Comments
Well... I guess the key is actually the additional remark you had at the end of the question. Yes, imho, all this is dependent on the fact whether the RS implements that feature. Is it clearer if I reformulate it slightly as in:
(And I agree the current formulation is unclear.) I would actually put an explicit reference to https://www.w3.org/TR/epub-33/#sec-escapability, which contains an elaborate example, too. |
Ivan's version of this is much better, but I'm still not clear on what escaping is other than the last phrase. Like, if you did the MUST, but not the last SHOULD, wouldn't that mean the user can't escape the content? It sounds to me like the last SHOULD is the definition of what escaping is, and therefore it should be a MUST. If I'm misunderstanding, then I think we need another MUST somewhere, because merely determining the start of nested structures — without any UI abilities — does not allow escaping. |
Yes, it's still a bit redundant with providing the feature. I would formulate it more along these lines:
Does this sound right to you, @marisademeglio ? |
Although, can an escapable structure be represented by a single Maybe it's better not to say what element to look for and make it:
|
What if we wrote something like:
This puts MUSTs and SHOULDs on measurable RS behavior. |
I think we need to say "or an ancestor" here, as if you're in a table cell there could be a Otherwise, sounds good to me. |
https://w3c.github.io/epub-specs/epub33/rs/#sec-escapability says (breaks and numerals mine):
It seems to me that #1 and #3 are saying the same thing. It's also not clear if the MUST is dependent on the SHOULD (like #2271), or if the MUST applies even if the RS doesn't support escaping.
The text was updated successfully, but these errors were encountered: