Engineer on @googlechrome. Involved in CSS and W3C standards. Previously @mozilla, @w3ctag. Mastodon: @dbaron@w3c.social
Rockville, Maryland, USA
Joined March 2008
- Tweets 7,521
- Following 1,244
- Followers 4,296
- Likes 18,519
Looks like an Antonov An-124 will be visiting Moffett Field sometime in late May.
Volga-Dnepr - Mountain View (Moffett Field)-NASA Shuttle Landing Facility, Titusville, FL Emergency Exemption Amendment: airlineinfo.com/ostpdf101/73…
2
1
...browser and works in the good browser, it's likely good to check after each step of this reduction that the minified version still has the bug and the unminified version still works correctly.
(It's useful because you might otherwise end up with code broken both ways.)
2/2
Reducing the @mavoweb side to something more minimal (if that's useful, not sure if it is) should be similar to reducing for a browser bug.
Just like it's useful when reducing for a browser bug to check after each step of reduction that it still shows the bug in the bad...
1/2
1
1
Er, ignore my previous (deleted) tweets on this topic; the mapping was done the right way around. /cc @ManishEarth
1
Current schedules have Daxing opening 3 months ahead of Crossrail (September versus December 2019), so Daxing seems like a pretty solid guess, at least.
1
The vote mostly agreed with that conclusion... although crossrail does seem like it has an outside chance at being first.
2
It was something in css-layout-api that was defining via 10-line-algorithm when you get a new object versus a cached one.
2
I want @googlecalendar to, after 2 minutes of inactivity, switch back to showing today rather than whatever other time period I was looking at.
(Yes, I added an event to next week that should have been today, and then planned my morning based on text Tuesday's schedule...)
2
12
They're great -- but the thing I wanted is different. I'd like bug tracking to be done in something more like a wiki and less like an email thread. I don't like the history being the primary view; I want the known state to be the primary view, with ability to see history.
4
While we as spec designers can't fix the bit about Edge not shipping font loading API yet, it would be interesting to understand what else to do here. What critical pieces can't you do declaratively? Are they things browsers are OK with? /cc @zachleat @mnot @tabatkins @jfkthame
1
1
It doesn't quite have the capacity Berlin needs, though. Nor, for that matter, does Brandenburg.
1
1
Also, is there an expectation for when the new character will be assigned in @unicode and how long we'll have from that point until it's heavily in demand?
Is this assigning unassigned codepoints, or making a breaking change (presumably one expected not to cause real-world breakage)?
2