W3C home > Mailing lists > Public > www-style@w3.org > April 2013

Re: [css-overflow][css3-regions] CSS Overflow covering CSS Regions use cases + [css3-gcpm]

From: Johannes Wilm <johannes.wilm@sourcefabric.org>
Date: Sat, 27 Apr 2013 16:10:31 -0400
Message-ID: <CAJYMer=X2QNsAf_=vS8Z=83gbQ19eStP42AavCzcybcK+pH1cA@mail.gmail.com>
To: Håkon Wium Lie <howcome@opera.com>
Cc: www-style@w3.org
On Fri, Apr 26, 2013 at 7:24 PM, Håkon Wium Lie <howcome@opera.com> wrote:

> I've coded the Malay Archipelago document in css3 + html:
>   http://people.opera.com/howcome/2013/tests/malay/archipelago.html
> Which results in this PDF document:
>   http://people.opera.com/howcome/2013/tests/malay/archipelago.pdf
> Also, it paginates in Opera 12.


> Would it be possible for book.js to read the css3 code and thereby
> implement footnotes, pagination and all the other goodies?

It is my understanding that Javascript, at least on Chrome, is not able to
access unsupported style declarations. So it would need to parse the CSS
itself and then find the parts that are interesting to it. Possibly this
could achieved with
http://sources.disruptive-innovations.com/jscssp/trunk/cssParser.js which
is about 170kb.

If it makes sense depends a bit on timing.
If CSS regions are likely to be available in Chrome without having to use a
flag a logn time before Opera's changes are merged into Blink, then this
will indeed make a lot of sense.

Whether this corresponds with the actual plan forward you guys at Adobe,
Opera and Google are more likely to know than me.

Johannes Wilm
BookJS Developer


US: +1 520 399 8880
skype: johanneswilm
Received on Saturday, 27 April 2013 20:11:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:29 UTC