- From: Florian Rivoal <florian@rivoal.net>
- Date: Sun, 14 Feb 2016 21:25:25 +0900
- To: Ivan Herman <ivan@w3.org>
- Cc: James Craig <jcraig@apple.com>, Shane P McCarron <shane@aptest.com>, Janina Sajka <janina@rednote.net>, W3C PF - DPUB Joint Task Force <public-dpub-aria@w3.org>
> On Feb 14, 2016, at 19:42, Ivan Herman <ivan@w3.org> wrote: > > Sigh. This stuff has a great potential, it would be a pity to let it go. It actually touches on a different area that the DPUB community also feels strongly about, namely the fact that in all ebook reader apps it is possible to change the font, the background colour, etc, of the display, whereas in browsers these facilities practically never exists. "Personalization", as we refer to it in our interest group. Facilities for changing the font, the background color, etc, exist in all browsers (except chrome which removed them not that long ago) in the form user style sheets. The UI is between horrible and non existent, but the mechanism for affecting the styling of the document has been in CSS since CSS 1. The kind of UI displayed by ebook readers is perfectly doable on top of user stylesheets. It's just that browsers don't care, as a streamlined UI seems to unlock much more market share that features and customization. Some disagree, and if you give a try to Vivaldi, they have a "page action" button that works sort of like that. But mainstream browsers are generally not going in that direction. I am very skeptical that a problem that seems to boil down to browsers not being interested in a feature can be solved by providing a different way of achieving the same goal, especially one that still leaves the UI up to the browsers. Offering hooks for more abstract preferences very well work, but for the more direct kind of changes, the technical problem was solved about 2 decades ago. The difficulty lies elsewhere. - Florian
Received on Sunday, 14 February 2016 12:25:51 UTC