Minutes New York F2F 2015-05-20 Part II: position: fragment, Flexbox Order Accessibility
position: fragment
- Rossen brought examples of why he believes that
position: fragment
(previously position: page
) should be a part of the Positioning spec.
- One of the main use cases that the working group felt needed to be solved is to make sure a page prints well, even if the author didn’t design for printing.
- The argument against position: fragment was that all the use cases would be better addressed by the Page Floats spec because it already has definitions of exclusions and avoidance.
- Page Floats itself, though, is underspecified right now and therefore it’s hard to decide for sure if it would actually solve the use cases.
- Many people agreed that Page Floats needs to be explained in terms of CSS primitives, basic concepts, that are generic that can explain other aspects of CSS layout.
- Resolved: Page Floats way better defined, less magic, as potential switches (even if not exposed)
Full Minutes || Specs Referenced: Positioning, Page Floats
Flexbox Order Accessibility
- Bo brought the concerns about Flexbox‘s ability to reorder visual layout running into accessibility concerns when that visual sequence change is important to the reader’s understanding.
- As the conversation progressed, tantek pointed out that this is a problem experienced by many specs, not just Flexbox, and the group turned to trying to see if there’s a solution that could fix it for all layout specs instead of focusing just on Flexbox.
- Bo will bring examples of broken pages to the group to see more of the exact problem and Tab will contact the WebApps group to explore a reordering API.
Full Minutes || Spec Referenced
« Previous article
Next article »