If in future CSS Regions levels we allow CSS Regions that are not block containers, several issues arise. Questions on some of these issues are captured here: http://lists.w3.org/Archives/Public/www-style/2012Sep/0555.html
A 'nobreak' value has been proposed for the region-fragment property: http://lists.w3.org/Archives/Public/www-style/2012Feb/0000.html
The region-order property was dropped from level 3 but could be reconsidered. There are cases (such as table layout) where the document order for the region chain is not the intended reading order. Allowing the author to specify the order of the region chain would be useful in those cases.
More CSSOM could be added based on use cases identified from use of level 3. One possibility could be closing the loop of going from region to ranges and back again. We currently have a method for retrieving the ranges in a particular region, but there is not a simple way to find out what regions a particular range flows through. https://www.w3.org/Bugs/Public/show_bug.cgi?id=16382