- From: François REMY <francois.remy.dev@outlook.com>
- Date: Sat, 7 Mar 2015 17:28:16 +0000
- To: Fantasai <fantasai.lists@inkedblade.net>, MURAKAMI Shinyu <murakami@antenna.co.jp>
- CC: CSS WG <www-style@w3.org>
- Message-ID: <DUB405-EAS1437853C17E51DE542C11C8A51D0@phx.gbl>
Hi, I’ve started reviewing the spec, and fwiw I think Issue 1 is handled properly at this time. I’ve also started some work to add diagrams to the spec. Here’s one I think we could use to visually represent the definitions: We could annotate the fragmentainers, the fragmentation context, the content flow, the fragmentation (arrow) as well as the remaining extend after the last element. What do you think? I was also thinking about adding diagrams to explain more phenomenons like parallel fragmentation: Ditto for the filling of the remaining fragementainer extent on break: Do you have any particular concern or comment before I proceed to expand the diagrams coverage proposal? Best regards, François ________________________________ PS: Please, feel free to help the spec by submitting better diagrams than mine if you feel like, I’m certainly not an expert at making diagrams, but I have enough interest in this spec to make sure at least someone does that work ;-) De : Fantasai Envoyé : samedi 28 février 2015 19:22 À : CSS WG, public-digipub-ig@w3.org, epub-working-group@googlegroups.com, MURAKAMI Shinyu The CSS WG has published an updated Working Draft of the CSS Fragmentation Module Level 3: http://www.w3.org/TR/css3-break/ This module describes the fragmentation model that partitions a flow into pages, columns, or regions and provides controls for breaking. We expect this to be the last WD before CR, and plan to transition at the end of March. Please review and send us any comments. If you plan to review but aren't sure you have time, send us a note so that we know to wait for your comments. We are particularly looking for feedback on * Which rules are dropped when breaks are overconstrained http://www.w3.org/TR/2015/WD-css3-break-20150129/#unforced-breaks * Anything that appears to be insufficiently specified or explained. We are particularly looking for reviews from * Anyone who makes a print or PDF output implementation. * Anyone who makes an eBook implementation. * Anyone who authors documents for such implementations. We will also welcome any submissions of better/more examples and diagrams. Significant changes since the last WD are listed at: http://www.w3.org/TR/2015/WD-css3-break-20150129/#changes Please send any comments to this mailing list, <www-style@w3.org>, and please, prefix the subject line with [css-break] (as I did on this message). For the CSS WG, ~fantasai
Attachments
- image/png attachment: Image1483.png
- image/png attachment: Image1490.png
- image/png attachment: Image1597.png
Received on Saturday, 7 March 2015 18:06:53 UTC