@tabatkins Could you please take a look at https://bugzilla.mozilla.org/show_bug.cgi?id=1315368#c3 … and following and tell me whether this is a Gecko, Chrome, or spec bug?
-
-
-
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 -
Are there any css wpt tests? I looked for position:sticky wpt tests recently and didnt find any.
1 reply 0 retweets 1 like -
I don't see any in https://github.com/w3c/csswg-test , which we run from WPT.
@gsnedders?2 replies 0 retweets 0 likes -
Replying to @larsberg_ @wanderview and
css-syntax specifically is hard because the tokenizer is not exposed to the platform.
1 reply 0 retweets 0 likes
Hard to unit test, but still testable.
-
-
Replying to @really_bz @bz_moz and
Yeah, just got to be clever with triggering syntax violations.
1 reply 0 retweets 0 likes -
Replying to @tabatkins @bz_moz and
I have unit tests at https://github.com/SimonSapin/css-parsing-tests … that can’t be ported to WPT.
0 replies 0 retweets 1 like
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.