- From: Alan Stearns <stearns@adobe.com>
- Date: Fri, 4 Oct 2013 11:27:49 -0700
- To: "www-style@w3.org" <www-style@w3.org>
- CC: Rossen Atanassov <Rossen.Atanassov@microsoft.com>
Rossen, We had an off-list conversation earlier this week where I promised to send a list of posts on css-break that need responses. Here it is: Minor editorial comments http://lists.w3.org/Archives/Public/www-style/2013Sep/0546.html Clarifications on break interactions http://lists.w3.org/Archives/Public/www-style/2013Sep/0438.html Rules for fragmenting overflow http://lists.w3.org/Archives/Public/www-style/2013Sep/0125.html Fragmenting and zero-height containers http://lists.w3.org/Archives/Public/www-style/2013Apr/0186.html More interop on overflow versus slicing http://lists.w3.org/Archives/Public/www-style/2013Aug/0276.html http://lists.w3.org/Archives/Public/www-style/2013Mar/0057.html Clarify whether break classes have priorities http://lists.w3.org/Archives/Public/www-style/2013Jul/0469.html Are line boxes within inline blocks break opportunities http://lists.w3.org/Archives/Public/www-style/2013Jul/0342.html Clarifying break propagation http://lists.w3.org/Archives/Public/www-style/2013Feb/0748.html (review entire thread) Quite a few of these are general fragmentation questions that have come up as we work on Regions, so I'm a little embarrassed about pushing this all off on you. If I can help with the fragmentation spec, please let me know. Thanks, Alan
Received on Friday, 4 October 2013 18:28:20 UTC