- From: Sylvain Galineau <sylvaing@microsoft.com>
- Date: Wed, 29 Jun 2011 15:51:08 +0000
- To: Daniel Weck <daniel.weck@gmail.com>, Tab Atkins Jr. <jackalmage@gmail.com>
- CC: "www-style@w3.org" <www-style@w3.org>
[Daniel Weck:] > > On 28 Jun 2011, at 19:25, Tab Atkins Jr. wrote: > > On Mon, Jun 27, 2011 at 12:55 PM, Daniel Weck <daniel.weck@gmail.com> > > wrote: > >> The solution based on a CSS pseudo-class was rejected on the basis > >> that it was impractical for reading system implementors. > > > > I don't understand what this reasoning means. Could you elaborate? > > -- Note that this statement does not reflect my personal opinion, I am > merely trying to relay ; as accurately as I possibly can ; the reasons > behind the consensus reached by the EPUB committee. -- > > Basically, some (but not all) EPUB reading system implementors within the > EPUB working group raised objections against the CSS pseudo-class > solution, on the basis that they wouldn't be able to easily implement > support for it, as it would require modifying the browser engine (other > regexp-based, content pre-processing "hacks" were deemed unsuitable too, > by the way). > > The EPUB3 specification process is public, so here are useful references > related to this particular issue: > > http://groups.google.com/group/epub-working- > group/browse_thread/thread/f25b73459500a63d > > http://groups.google.com/group/epub-working- > group/browse_thread/thread/1eba33a3b544b6e2 > > http://groups.google.com/group/epub-working- > group/browse_thread/thread/826af2152a60aa46 > > Regards, Daniel > So the solution is driven by where it would have to be implemented and who is able/unable to do that ?
Received on Wednesday, 29 June 2011 15:51:40 UTC