search

w3c / epub-specs

Shared workspace for EPUB 3 specifications.
Other
307 stars 60 forks source link

Scripting: "Interoperability": defined behaviour of window.scrollTo #88

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
CONTEXT

The EPUB spec has (since at least version 2) encouraged paginated contexts for 
component documents. EPUB 3.0 asserts that it has real interoperability for 
scripting — which is important, because without real interoperability, the 
dominant implementation will effectively set the rules and any standards body 
becomes superfluous.

THE PROBLEM

In EPUB 3.0 Scripted Content Documents, what is the expected behaviour of 
window.scrollTo in paginated contexts? scrollTo is used by a number of reading 
systems to handle pagination, therefore scripted use of scrollTo would break 
this functionality. Does the WG recommend that these reading systems find 
another way to do pagination? 

Some reading systems modify the DOM so as to display a single page of text. 
Other elements are hidden or removed from the DOM. scrollTo would also break 
this mode of pagination. Does the WG also prohibit this method of pagination in 
order to achieve interoperability?

Original issue reported on code.google.com by josephpe...@gmail.com on 21 Feb 2011 at 9:42

GoogleCodeExporter commented 9 years ago 
This issue was discussed by the WG. The decision was that IDPF does not want to 
introduce any changes to W3C scripting model. This is one of the reasons why 
scripting in spine-referenced content is non-interoperable (the spec should 
talk about it). Interoperability of scripts is only guaranteed in nested 
content (e.g. XHTML referenced by an iframe element).

Original comment by soroto...@gmail.com on 24 Feb 2011 at 9:35

GoogleCodeExporter commented 9 years ago

Original comment by markus.g...@gmail.com on 8 Mar 2011 at 9:59

GoogleCodeExporter commented 9 years ago 
members of the WG discussed this again and it was decided not to change the 
specification at this point. We do not see altering W3C scripting model to 
accommodate paginated content as viable path. As paginated environments are 
becoming more common, this should be addressed at W3C level.

Original comment by soroto...@gmail.com on 19 Apr 2011 at 4:43