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
What if there's more than one "rest of W3C", each disconnected from the other?
(I think that's been true in the past and may still be the case today.)
2
1
I hope that means that at least one person was able to understand it. (It was still probably too long. And I've since thought of a better way to explain the "half a step" difference)
1
L. David Baron @dbaron@w3c.social retweeted
My view departs from urbanist consensus here in that the solution to this involves much more enforcement. That that term conjures up armed, immunized agents of the state rather than unarmed, automated cameras is a product of law & politics, not something intrinsic to enforcement.
New: U.S. traffic deaths soar in 2021 -- up 18.4% in first half of 2021 as American drivers continue more unsafe driving that began during the pandemic lockdowns
4
11
4
104
The TAG probably doesn't have the bandwidth, but it would be good to have a step (around CR) that requires one person who didn't write or edit the spec to read and review it thoroughly.
1
2
AC review generally isn't the stage where specs get read carefully.
The W3C process could use a better mechanism for detailed review, like WHATWG code review or maybe IETF AD review. It's easy for things to get to REC because everybody is happy with the general idea.
1
5
Still, the total capacity of Marin's 7 reservoirs is 1/44 that of Lake Oroville or 1/57 of Lake Shasta. Being in a rainier area does help.
1
IIRC Marin's reservoirs fill fast (large watershed area / reservoir volume) and drain fast (small reservoir volume / demand).
1
5
First time ordering sushi since this thread, and I notice this on the menu. (I didn't order any of these, though.)
1
2
I was born in Pennsylvania so I'm definitely not Pennsylvania-avoidant.
(I've excluded states that I only traveled through and didn't have a destination in.)
1
For those following along, here's the log of spec edits: github.com/w3c/csswg-drafts/…
Yes, you'd like me to publish the spec on TR. I'd like to do so soon, but hopefully address a few other things first.
1
These are steps towards making 3D transforms more predictable for developers and more interoperable between browsers. Other browser engines have been making progress on this path too, and there should be more to come.
1
1
15
In Chrome 94, the changes (started by @chrishtr) described in groups.google.com/a/chromium… and docs.google.com/document/d/1… shipped, changing how transform-style:preserve-3d and perspective interact with the DOM tree.
1
1
4
In Chrome 93 values less than 1px of the perspective property and perspective() transform function get clamped to 1px, and 0 is no longer special. For more information see the post at groups.google.com/a/chromium… and the change at chromium.googlesource.com/ch… .
1
1
7
Lately I've been working on CSS 3D transforms in Chrome (and on the CSS spec at drafts.csswg.org/css-transfo… ). A few of the things I've been working on have shipped recently in Chrome. (Thread)
2
11
65
L. David Baron @dbaron@w3c.social retweeted
Another RenderingNG deep-dive for you! This time on LayoutNG, our brand-new, compete rewrite of all of layout for massively improved reliability and extensibility for future use cases. By @bfgeek and @kojiishi, with another cool illustration from @Una.
developer.chrome.com/blog/la…
2
25
2
106