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

The EPUB 3.1 spec should address common reader styling scenarios #671

Closed
ryanackley opened this issue Feb 15, 2016 · 4 comments
Closed

The EPUB 3.1 spec should address common reader styling scenarios #671

ryanackley opened this issue Feb 15, 2016 · 4 comments

Comments

@ryanackley
Copy link

@ryanackley ryanackley commented Feb 15, 2016

As an implementor on the Readium EPUB viewer, one thing that was noticeably absent in the spec was how to handle reader preferences.

For example these three things were configurable in the readium epub reader: font size, background color, and font color.

There is no one way to deterministically set these properties in every epub content document. This is because the spec does not address this scenario in spite of almost every epub reader allowing users to change these styling properties.

It's a matter of overriding the author's css which isn't incredibly difficult but there are many edge cases and it feels overall like a very hacky approach.

@dauwhe
Copy link
Contributor

@dauwhe dauwhe commented Mar 3, 2016

Are there issues with the CSS cascade and the concept of user styles which are inadequate to the task at hand?

@JayPanoz
Copy link

@JayPanoz JayPanoz commented Mar 17, 2016

Hi there, just providing a small example of default CSS used for user styles you can find in a RS:

  body {
    margin: {margin}px !important;
  }

  *, * *, *[class], *[class] *[class] {
    background: transparent !important;
    background-color: transparent !important;
    border-color: {foreground-color} !important;
    line-height: {line-height}% !important;
    text-align: none !important
  }

  html, html * {
    color: {foreground-color} !important;
  }

  a[href], a[href] * {
    color: {anchor-color} !important;
    text-decoration: underline !important;
  }

That is the most insane I've found for the moment—yep, we are indeed collecting RS' default CSS —but imho, we may have got a bigger than expected problem here… Or in other words, how can we even rely on the concept of cascade if RS are doing that?

@mattgarrish mattgarrish added this to the EPUB 3.1 milestone Apr 14, 2016
@mattgarrish mattgarrish added this to the EPUB 3.1 milestone Apr 14, 2016
@dauwhe
Copy link
Contributor

@dauwhe dauwhe commented Jun 30, 2016

I don't think there's anything we can do in the context of the 3.1 revision. Personalization on the web is a large problem, and will require coordination between CSS, the A11Y community, etc.

@dauwhe dauwhe removed this from the EPUB 3.1 milestone Jul 13, 2016
@wareid wareid added the Agenda+ label Jun 23, 2021
@iherman
Copy link
Member

@iherman iherman commented Jun 25, 2021

The issue was discussed in a meeting on 2021-06-24

  • no resolutions were taken
View the transcript

3. The EPUB 3.1 spec should address common reader styling scenarios

See github issue #671.

Wendy Reid: i was looking through the issue list and we've only got a few issues still open
… and most are still recent
… this one we might be able to close after some brief discussion?
… someone asked if spec could address common "reader styling scenarios"
… so, if you have a library of ebooks, how to ensure consistency across that library
… it's an interesting problem, but probably out of scope for the epub spec

@dauwhe dauwhe removed the Agenda+ label Jul 7, 2021
@dauwhe dauwhe closed this Jul 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants