You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As discussed on the 2023-01-05 telecon, there are support gaps for the dir attribute in the package document. Looking at the tests, these failures appear to all be centred around support for the rtl value.
Consequently, rather than mark the whole attribute under-implemented, this PR only adds the label to the rtl value. This is in keeping with how the portrait value for rendition:spread is deprecated.
If I've misread the test results and we need to consider a whole-attribute labelling, please feel free to say so, though.
And as this looks like it could be the only under-implemented feature we'll have, and we want reading systems to support it moving forward, it doesn't make sense to me to label it in the Reading Systems specification. It seems to undermine the goal of getting support improved. Can we limit ourselves only to warning authors? And, similarly, can we remove the text in the RS appendix about not having to support under-implemented features?
…ote explaining why it is still important to set;
adds note to the RS spec to explain that reading systems need to support the attribute despite the authoring label
The reason will be displayed to describe this comment to others. Learn more.
I guess this is based on getting to an equilibrium point on MO, ie, that there is no under-implemented notion for MO at all (which is probably all right, because MO is not a required feature as a whole).
The reason will be displayed to describe this comment to others. Learn more.
Either that or we do something similar where we under-implement the authoring feature. I made that change after the last call when it sounded like we wouldn't have to label MO because it's only a recommended feature. It's easy to get back the prose if we need it, though.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As discussed on the 2023-01-05 telecon, there are support gaps for the
dir
attribute in the package document. Looking at the tests, these failures appear to all be centred around support for thertl
value.Consequently, rather than mark the whole attribute under-implemented, this PR only adds the label to the
rtl
value. This is in keeping with how theportrait
value forrendition:spread
is deprecated.If I've misread the test results and we need to consider a whole-attribute labelling, please feel free to say so, though.
And as this looks like it could be the only under-implemented feature we'll have, and we want reading systems to support it moving forward, it doesn't make sense to me to label it in the Reading Systems specification. It seems to undermine the goal of getting support improved. Can we limit ourselves only to warning authors? And, similarly, can we remove the text in the RS appendix about not having to support under-implemented features?
Preview | Diff