- From: Greg Whitworth via GitHub <sysbot+gh@w3.org>
- Date: Mon, 31 Oct 2016 16:28:28 +0000
- To: public-css-archive@w3.org
Before digging in too deeply on this, why is this _needed_? Is this a common pattern that authors are having to fight against, requesting of UAs, etc? Since tables currently focuses on fragmenting on the row, I'd doubt that writing modes which reside inside of the rows will have much affect on how we're fragmenting, but I haven't done much investigation here though - so I could be wrong and have been wrong numerous times before when investigating table issues. Based on your answer to the use case question above, I'd rather shore up the holes in our spec (if any, we already specified more than what was currently specified) so that this will leave the Break Editors free to define what they think is best for the most common use cases in this space. Because, I really don't think this is table specific, you'll have this same issue with Grid. I've filed a bug on us to look into writing modes, and please let us know if there are any other fragmentation issues you feel aren't specified and we'll investigate them accordingly: https://github.com/w3c/csswg-drafts/issues/669 -- GitHub Notification of comment by gregwhitworth Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/367#issuecomment-257343314 using your GitHub account
Received on Monday, 31 October 2016 16:28:36 UTC