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
Please revise #AB161 so that retailers aren't allowed to retain the contact information (email addresses or phone numbers) longer than needed to send the receipt.
Otherwise consumers will be afraid to provide their email addresses for fear of getting more spam.
3
3
There are laws in many parts of the US forbidding charging for public bathrooms -- which in turn reduces the number that are provided since it's harder to justify maintaining them (or maintaining them well).
1
3
And then some, like Palo Alto, have a lot of unpopulated or barely-populated area:
openstreetmap.org/relation/1…
Probably the parts between Foothill Expressway and 101 (or, more so, El Camino Real and 101) are close to that density.
2
A photo of an urban environment I like:
rue Caulaincourt & rue des Saules & rue Lamarck, 75018 Paris, France
1
4
One thing American was thinking is that some of the new aircraft models they ordered weren't actually metal (instead, composite), so the "bare metal" look absolutely had to go.
That said, I wish they kept the design and just had it on a white background...
2
2
I tried for a few hours, but it was weird. Switched back to QWERTY on mobile despite using Dvorak on desktop.
Though, somewhat related, the working group has attempted to document property computed value dependencies at wiki.csswg.org/spec/property…
1
I think the thing you're proposing would require that selector matching (which is expensive) happen in multiple passes, and then cascading (also somewhat expensive) happen again after each pass to resort the resulting results.
2
Would be amusing to have more Finns respond directly to nitter.vloup.ch/NikkiHaley/statu… :-)
Alright @BernieSanders, you’re not the woman having the baby so I wouldn’t be out there talking about skimping on a woman when it comes to childbirth. Trust me! Nice try though.
I think the US reality is even worse: you can go straight to the database, but only if you're willing to give your data to a private company to interact with the government for you, rather than dealing with the government directly.
This is why I file my taxes on paper...
1
e.g., normal in-flow content, in-flow content that has an ancestor whose height has already finished on a previous page, pieces of floats that began on a previous page, entire floats that couldn't even start on the previous page (don't get them out of order!), etc., etc.
2
... where in a certain case you forgot to deal with moving a piece of content over to the next page and just left it on some list of things that needed to be handled. There are just lots of categories of stuff...
2
1
The latter is hard because it requires a good understanding of the full range of what CSS can do. You need to know all the cases, because if you don't you'll end up with dangling pointer bugs, at least logically if not actually, because you end up with bugs of the sort...
1
1
There are two+ disconnected parts to the printing code:
* interaction with printer drivers, the OS, and things like print settings and paper sizes
* how to break up HTML/CSS across pages
Bob Owen has done a bunch of good work lately on the former; I probably (!) own the latter
2
1
There's also some interesting work on web packaging happening now. I think seeing it as an alternative for PDF and for "Save As... complete" is an important use case, though others are the focus right now, and the security properties of those other use cases are controversial.
1
1
At the same time, implementing CSS to print well is hard and a lot of work, and hard to get people to believe it's a good investment relative to other ways to improve the web. Gecko's architecture could be improved, but I hear similar things about difficulty from other engines.
1
1
Generally users expect the former (and most web page authors don't care about printing), whereas people who actually want to do print stuff on the web want the latter. We've mostly made decisions to match the user expectation, but as a result the developer facing API is ugly.
1
1