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

Clarify scripting support contexts #660

Closed
mattgarrish opened this issue Jan 28, 2016 · 0 comments
Closed

Clarify scripting support contexts #660

mattgarrish opened this issue Jan 28, 2016 · 0 comments
Labels
EPUB32 Issues from 3.0.1 resolved in the EPUB 3.2 specification Topic-ContentDocs The issue affects EPUB content documents
Milestone

Comments

@mattgarrish
Copy link
Member

EPUB currently requires support in container-constrained contexts (iframe, object, embed) and leaves spine-level scripting optional.

EPUB 3.1 makes the following changes:

  • container-constrained scripting is limited to iframe
  • container-constrained scripting becomes a should
  • spine-level scripting in fixed-layout documents becomes a should
  • spine-level in reflowable documents becomes a should if the documents use the scrolled-doc or scrolled-continuous interfaces defined by the rendition:flow property
  • if spine-level scripting is support for reflowable documents, the scrolled-doc interface must be supported and scrolled-interface should be supported

Whether scripting is a "should" or "must" may change in a future draft if a security and privacy model are worked out.

For more information, see the scripting group's working document.

@mattgarrish mattgarrish added the Topic-ContentDocs The issue affects EPUB content documents label Jan 28, 2016
@mattgarrish mattgarrish added this to the EPUB 3.1 milestone Jan 28, 2016
@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