search

w3c / publ-cg

EPUB 3 Community Group Repository
Other
44 stars 16 forks source link

[Interop] Prefixed properties #23

Closed llemeurfr closed 6 years ago

llemeurfr commented 6 years ago

Please consult https://github.com/readium/readium-css/issues/32, which has the same title (we'll keep it to summarize the conclusion of this thread in the scope of Readium CSS).

The crux of the issue is that distributors shouldn't ask EPUB authors to harm interoperability by asking constrained EPUB implementations. It this case, the issue is about prefixed properties (e.g. those required for handling vertical writing). But it could be in other domains of CSS, or why not HTML5.

We think that such issue must be escalated to the EPUB 3 CG, acting as a "WHATWG-style" forum for enhancing the interoperability of reading systems. What should the CG do for such issues? can it act as a hub where authors, distributors/booksellers (Google in this case) and reading system developers can settle on good practices?

Related threads: https://github.com/readium/readium-css/issues/19 https://github.com/readium/readium-css/issues/26

GarthConboy commented 6 years ago

And, FWIW, I added an issue the readium/readium-css/32 -- there should be no such issue from a Play Books perspective.

llemeurfr commented 6 years ago

Thanks @GarthConboy, it means that this CG can indeed act as a forum for resolving EPUB interop issues, which is great!

llemeurfr commented 6 years ago

This issue can now be closed, as it'll soon be resolved by the distributor.