Engineer on @googlechrome. Involved in CSS and W3C standards. Previously @mozilla, @w3ctag. Mastodon: @dbaron@w3c.social

Rockville, Maryland, USA
Joined March 2008
Filter
Exclude
Time range
-
Near
Replying to @ManishEarth
That was my experience too, maybe a year or two after Charlie Cards came out (which was after I no longer lived there). (I remember when tokens went up from 85¢ to $1.)
1
Replying to @sunshowers6
The lab I used most often ran Compaq Tru64 Unix (previously known as DEC OSF1) on machines with Alpha CPUs... but it was replaced summer 2002 (or maybe 2001) with machines running some Linux distro on Intel CPUs. Also sometimes used a lab with Macs for testing browsers.
For what it's worth,I find the original stated rationale somewhat weak (that is, why not just sort them in the middle?), although I think there may have been more to it that I've forgotten.
1
Last 2 paragraphs of w3.org/TR/CSS1/#the-cascade are the best I know of the original rationale. But turns out it's also good for clarity around lexically scoped features like @namespace (IIRC the CSS WG was discussing a new one last week or so).
2
2
I don't know about law, but it does sound like it's the norm.
1
Seems like China is more extreme than the US; Chinese relatives were unhappy we weren't masking our 1 year old (12 months old at the time).
1
1
Replying to @MikeHommey
Perhaps that means "we" changed how we pronounce "break" sometime in the last 600 years?
Replying to @seungylee14
Would also be nice if the Bay Area's population were a little closer to Chongqing's... Context: en.wikipedia.org/wiki/Liziba…
1
1
10
SF has some historic trolleys running on the F-Market and E-Embarcadero lines. The other streetcar lines (J/K/L/M/N/T) are indeed modern ones, though.
1
1
2
Replying to @MarijnJH
I thought a bunch of the ideas were Incorporated into other APIs, but don't remember. I had hoped to investigate briefly today, bit didn't get the chance. Maybe tomorrow...
1
1
The first group can be subdivided into those who find much daikon bitter (hi!) and those who don't.
1
2
Replying to @meyerweb
So... how many houses do kids in your neighborhood typically visit? (Are you located to get lots of kids from other neighborhoods, or do kids there get lots of candy?)
Meanwhile in San Francisco it's sometimes just some yellow paint on a post with black stenciled letters.
8
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
Replying to @fantasai
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
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
Replying to @jyasskin
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
Replying to @khuey_
Let me know when you're ahead of me on total rainfall since I moved out of the Bay Area.
Replying to @luis_in_brief
Evergreen:
Replying to @roessler
Among my favorite Proposition 65 warnings are the ones in 99 Ranch: