A story of web standards in 4 acts: 1) Compat concerns are raised with a change to the flexbox spec: https://lists.w3.org/Archives/Public/www-style/2014Jul/0589.html …
-
Show this thread
-
2) Google rep to CSSWG replies "author just needs to fix their content": https://lists.w3.org/Archives/Public/www-style/2014Aug/0282.html …
1 reply 5 retweets 4 likesShow this thread -
3) Chrome implements something different from the new spec: https://bugs.chromium.org/p/chromium/issues/detail?id=487302 …
1 reply 5 retweets 5 likesShow this thread -
4) Chrome team creates a site about browser compat that fails in Firefox and Edge by depending on the Chrome bug:https://github.com/GoogleChrome/confluence/issues/165 …
1 reply 8 retweets 8 likesShow this thread -
And all this is with the best of intentions from everyone involved, as far as I can tell.
1 reply 4 retweets 4 likesShow this thread -
Replying to @really_bz @bz_moz
Does the
@csswg create tests and file bugs for any normative changes?3 replies 0 retweets 1 like -
I wish. They have had an explicit policy of editors NOT filing bugs, actually, and saying that's the responsibility of the browsers' reps.
2 replies 0 retweets 6 likes -
Replying to @really_bz @bz_moz and
This "policy" is a result of the fact that most specs are edited by just two people, and we're already overloaded with work.
3 replies 0 retweets 1 like
I understand that. We really need more people than just you and @fantasai editing!
-
-
Replying to @really_bz @bz_moz and
The situation is improving over time. :) But it's slow, & layout specs in particular are difficult to do well.
1 reply 0 retweets 0 likes -
You need both a deep & broad understanding of CSS to make good design decisions and integrate everything properly. That takes time to build.
0 replies 0 retweets 0 likes
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.