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 @rem
@rem Just make such a font and use it? ('unicode-range' descriptor optional.)
Replying to @sayrer
@sayrer Code should either wrap at < 80 cols or not wrap at any length. I strongly dislike manually wrapping at > 80.
1
Replying to @meyerweb
@meyerweb @t @svgeesus The two now missing aren't exact conversions, so maybe hard to show clearly. Also hard to revise a REC: maybe css4?
Replying to @meyerweb
@meyerweb Though it's not actually rendering, it's asking for the glyph's extents.
1
Replying to @meyerweb
@meyerweb We do have 'x' measuring code for some platforms (maybe even all but Mac; not all cases though), though 'o' would be better
Replying to @beltzner
@beltzner @joedrew Yes, but if you miss the LRV, can you catch it at the next intersection by chasing it? (If so, it's less useful.)
Replying to @Boriss
@Boriss I think it's more a plan for the government to get its hands on hard (i.e., foreign) currency any way it can.
Replying to @tabatkins
@tabatkins I'd restate as: "eleven" plus "two" is an anagram of "twelve" plus "one", and if you remove a kind of letter, also of "teen".
1
@tabatkins Now, I see the removal is "plus vowel", but I'm still confused by the additions.
Replying to @tabatkins
@tabatkins You mean remove e, l, l, o, p, s, u, v, w, and add h, i, r, t?
1
Replying to @lxt
@lxt Is it one of those cases where the IAD-YOW alone would be more expensive?
2
Replying to @meyerweb
@meyerweb No, we dropped support for the prefixed version; you have to use background-size: cover now.
1
Replying to @meyerweb
@meyerweb FWIW, the spec for that has only been stable and in CR for just over a year. (It changed substantially from the previous CR.)
Glad I marked bugzil.la/742736 as [good first bug], and hopefully @stringsn88keys will find a good second bug too.
2
2
2
I feel like I ought to read LBJ vol. 4 amazon.com/dp/0679405070/ sooner rather than later; curious if Caro will stick to the 5-volume forecast.
Replying to @meyerweb
@meyerweb Anyway, please don't use localStorage; use IndexedDB instead
1
1
Replying to @meyerweb
@meyerweb maybe cookie and localStorage APIs should have been asynchronous, but Web developers seem to hate that.
1
Replying to @kizmarh
@kizmarh Sounds like misuse of the property and likely to lead to problems.
2
Replying to @meyerweb
@meyerweb We can't ask the user questions in the middle of a synchronous API implementation, since the API needs an immediate answer.
1