Added a new information item for progression direction. #142
Conversation
Relates to issue #126
iherman
requested review from
HadrienGardeur,
danielweck,
mattgarrish and
dauwhe
|
LGTM ! |
|
As @BigBlueHat mentioned on the call, there are only two values for page progression direction. Within HTML resources, CSS does allow for overflow in both x and y axes. If a publication resource scrolls "down," it might be a better reading experience for the next resource to appear below. Do we need a "top to bottom" direction? |
|
How about set default direction to "Reading System can choose default direction" which is same as idpf defined in http://www.idpf.org/epub/30/spec/epub30-publications.html#sec-spine-elem? It mightbe convenient when we need to convert from idpf to web infoset. Totally agree with adding the new information item |
…ogression * 'master' of https://github.com/w3c/wpub: Change orcid img to a text label until rendering can be resolved fix unclosed dl list Added the WP address as a requirement in our WebIDL Linking issues to affordances' sections # Conflicts: # index.html
|
@rakutenjeff : I am fine with what you propose and happy to do it if we have a consensus on the PR overall... |
|
My take is we merge this PR and continue to work out any additional details in separate issues, so that's what I'll do. :) Nothing is written in stone yet. |
|
Thanks @iherman Do you mind if I record it as a new issue since this is merged? Beside the default progression I was hoping wpub could have consistency with epub. And further more, my image of relationship between wpub and epub is wpub define what should be in manifest (and maybe define json serialization as well), and epub address those manifest items in packaged wp (epub) domain. So the manifest should be compatible. One of benefit is current publisher who already has millions of epubs would be easy to step into WP stage in the future. |
|
@rakutenjeff of course, by all means! Please do. |
ghost
mentioned this pull request
Fixes issue #126
Preview | Diff