Done, TR is TRash, as usual. :(
-
-
Replying to @tabatkins
Well, did people file bugs on UAs when the ED changed? Because 4 months ago you told me something that doesn't match today's ED.
3 replies 0 retweets 0 likes -
Replying to @really_bz @bz_moz
I doubt that I did; this change was from well over 4 months ago.
2 replies 0 retweets 0 likes -
Replying to @tabatkins
We talked about it, and then I implemented based on our conversation and the spec you linked me to at the time. Doesn't match ED
2 replies 0 retweets 0 likes -
Replying to @really_bz @bz_moz
I don't think I would have linked you to the TR version, tho. My muscle memory for CSS specs is pretty strong, always goes "dev.w3…"
1 reply 0 retweets 0 likes -
Replying to @tabatkins
Dunno. I was clearly left reading the TR version after our conversation. This crap all needs tests so desperately. :(
3 replies 0 retweets 1 like -
Replying to @really_bz @tabatkins
_Especially_ if the spec has said something else for 2 years and no one bothered to file UA bugs when that changed. :(
1 reply 0 retweets 0 likes -
Replying to @really_bz @bz_moz
I've never filed UA bugs because I changed a spec, in my 8 or so years of speccing. I didn't know that was even expected!
2 replies 0 retweets 0 likes -
Replying to @tabatkins
The various WHATWG editors have been doing that. It helps a _lot_ with making browsers realize the spec changed. ;)
1 reply 0 retweets 0 likes -
Replying to @really_bz @tabatkins
Anyway, if CSSWG could do it, that would be cool. If not, but can update web platform tests, that would be nice. If not....
1 reply 0 retweets 2 likes
At some point someone needs to notice that a draft changed 2 years ago _and_ it's time to implement that. How, is the question.
-
-
Replying to @really_bz @tabatkins
(Leaving aside the issue of 2-year-old drafts that are still at ED, because my WebIDL glass house can only take so many stones.)
0 replies 0 retweets 5 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.