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
Depends on the voting system used to count the ranked choice votes, I think.
With STV it's fine to cast a protest vote for a third party that has no chance.
But once it's not clear who the final two are, strategic voting is important again.
1
1
This reminds me of engineering-wide emails at Mozilla (many iterations of management ago):
Don't break builds/tests so often
or a few months later:
Don't use so much machine time on try runs
Both messages needed to be targeted. (And they weren't even hard conversations!)
This seems like a common management failing: blasting out feedback intended for specific employees to everyone because you don’t have the, um, guts to have hard one-on-one conversations. joshbarro.com/p/digital-reve…
2
10
The engineers working on shipping it in Chrome showed that it was a lot harder than I thought it would be... but it was, in fact, possible.
(See github.com/w3c/csswg-drafts/… for just one example. It turned out that the way CSS Transitions are started wasn't compatible with CQ.)
1
1
Getting a lot of mentions today about Container Queries shipping in Chrome. It feels a little odd given that it's something I haven't been very involved in for the last 2 years... though I did help start it down its path by claiming an approach was possible to implement.
1
7
I was able to figure out what changed MXCSR once I knew that was the problem. I don't remember how I did it, but maybe it helped that in my case it was a push/pop change that was on the assertion failure's stack, so I could just go up the stack in gdb+rr. bugs.chromium.org/p/chromium…
1
1
There's some relevant spec discussion on this in github.com/w3c/csswg-drafts/… and github.com/w3c/csswg-drafts/… although it's not specific to cascade layers.
2
There's a good bit of CSSWG discussion of this in github.com/w3c/csswg-drafts/…
1
The entire value of the 'transform' property (even if it's 'matrix() rotate() scale() matrix() matrix() perspective()') ends up as a single transform node in this tree. The things that have separate nodes are the 'rotate'/'translate'/'scale' *properties* (not *functions*).
1
Using 'will-change: rotate' means we'll create a node in the transform tree for the 'rotate' transform for that element, which means when you actually set 'rotate' the node will already be there, and less work will need to happen.
1
1
The nodes for 'rotate' and for 'transform' are separate so that they can be animated independently.
There is various work that happens when these nodes are created or destroyed. (There are perhaps some cases where some of it could be optimized away...)
1
We have a data structure called the transform tree that represents all of the "interesting" transforms. (There are actually two different versions: one in blink and a more limited one in the compositor.) This is the data structure where the compositor animates transforms.
1
Agree. Often does nothing, often works.
When I worked on the top (7th) floor of the Hills Brothers Building, when leaving work, I generally stood by the buttons on the side with good view of those waiting, and used the close button to get the elevator down 10-15 seconds faster.
1
I think it also varies by country.
IIRC in Japan it was not uncommon to be able to unselect a destination floor by pressing the lit-up button again. (And the close door buttons in hotel elevators generally work.)
1
1
You should have no problem claiming Alexandria, Virginia.
maps.app.goo.gl/4PcE46AeV1K4…
1
1
Didn't know they extended the Metro to Lewisham. Might be worth it to get to the Taronga Zoo, if it doesn't take too long. (After all, flying is 20 hours plus a layover.) Better zoo than the National Zoo.
(More seriously, we had a good bit more rain one day last week.)
HTML and CSS today are also very different from the way they were in 2000; now the fault tolerance is clearly specified and interoperable, rather than varying between implementations due to being left (particularly in HTML's case) up to the implementation.
1
3