Another reason to avoid @w3c TR drafts: they add a rule to float all ID selectors to the right: w3.org/TR/2015/WD-css-flexbo…
2
2
@davidbaron @w3c Seriously just puzzled at why it was put in. It's not part of W3C styling (wrong stylesheet); why add it?
1
Replying to @tabatkins
@tabatkins @w3c It's a broken process: random changes to specs, without public VCS visibility or knowledge of editors.

Jun 2, 2015 · 11:42 PM UTC

2
1
Replying to @davidbaron
@davidbaron And no one has ever meddled with drafts at the organisation level. If you're seeing those issues, they're just in CSS @tabatkins
1
@robinberjon @tabatkins Long history of team contact messing with drafts to satisfy the webmaster & not telling group/editor.
2
more replies
Replying to @davidbaron
@davidbaron @tabatkins That's completely a CSS WG issue. With Echidna, @w3c gives direct write access to TR for editors.
1
2