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

A deprecated property is still listed as an epubReadingSystem property. #874

Closed
tkanai opened this issue Sep 12, 2016 · 1 comment
Closed
Labels
EPUB32 Issues from 3.0.1 resolved in the EPUB 3.2 specification Topic-ContentDocs The issue affects EPUB content documents
Milestone

Comments

@tkanai
Copy link

tkanai commented Sep 12, 2016

According to the Content specification Appendix B, the layoutStyle property has been deprecated and asked to refer to the Content 3.0.1 specification.
But, Appendix A still lists the property in IDL Section. Since no appropriate prefixes which say the property is deprecated are available in Web IDL, the layoutStyle property should be removed.

@mattgarrish mattgarrish modified the milestone: EPUB 3.1 Sep 12, 2016
@mattgarrish mattgarrish added the Topic-ContentDocs The issue affects EPUB content documents label Sep 12, 2016
@mattgarrish
Copy link
Member

Yes, this is related to #799. I missed the inclusion in the IDL, but we've been moving all definitions of deprecated/superseded features to the appendixes.

I'm a little worried people might not pay attention to these appendixes, so might miss that these still have to be supported, but it's the path we've chosen to unclutter the specifications with obsolete feature definitions.

mattgarrish added a commit that referenced this issue Sep 14, 2016
#870 - clarify white space in epub:type
#866 - clarify hyperlinks outside container do no get listed in manifest
#855 - remove normative keyword from informative discouraged constructs
#853 - separate/clarify rdfa and microdata usage and support
#847 - improve media overlays purpose and scope description
#844 - remove "user" as a defined term
#842 - clarify meaning of element "value" as text content
#834 - remove html processing model from relationship description

Also include minor wording clarifications suggested as part of the content documents review in issues #880, #879, #878, #877, #876, #875, #874, #868, #867, #864, #863, #860, #857, #856, #852, #849 and a few issues reported by via the mailing list.
@mattgarrish mattgarrish added the EPUB32 Issues from 3.0.1 resolved in the EPUB 3.2 specification label Aug 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EPUB32 Issues from 3.0.1 resolved in the EPUB 3.2 specification Topic-ContentDocs The issue affects EPUB content documents
Projects
None yet
Development

No branches or pull requests

2 participants