A good editor's response to "I didn't understand this part of your spec" might occasionally be "You need to read this other part first", or "You need to slow down and read more carefully"...
...but most of the time it's "I will clarify it".
fantasai
@fantasai@w3c.social
mastodon
4.5.8
I hack CSS: W3C CSSWG specwriter 2004– // Mozilla layout engine QA & coding 1999–2013
0
Followers
0
Following
Joined December 16, 2022
Posts
fantasai
@fantasai@w3c.social
I hack CSS: W3C CSSWG specwriter 2004– // Mozilla layout engine QA & coding 1999–2013
w3c.social
3
1
0
fantasai
@fantasai@w3c.social
I hack CSS: W3C CSSWG specwriter 2004– // Mozilla layout engine QA & coding 1999–2013
w3c.social
QOTD: “If you don’t tackle the hard questions at dinner time, when are you going to solve them?”
0
0
0
fantasai
@fantasai@w3c.social
I hack CSS: W3C CSSWG specwriter 2004– // Mozilla layout engine QA & coding 1999–2013
w3c.social
7
0
7
fantasai
@fantasai@w3c.social
I hack CSS: W3C CSSWG specwriter 2004– // Mozilla layout engine QA & coding 1999–2013
w3c.social
2
0
0
fantasai
@fantasai@w3c.social
I hack CSS: W3C CSSWG specwriter 2004– // Mozilla layout engine QA & coding 1999–2013
w3c.social
@tantek.com@tantek.com Several of these choices represent the same time…
My answer is 2024/3/20 if it’s picking a day, 2024/3/19 11:06pm if it’s a time because I’m on the East Coast. Wrt “How do pick the day?”, it’s whichever calendar day the equinox lands in Iran.
My answer is 2024/3/20 if it’s picking a day, 2024/3/19 11:06pm if it’s a time because I’m on the East Coast. Wrt “How do pick the day?”, it’s whichever calendar day the equinox lands in Iran.
0
0
0
fantasai
@fantasai@w3c.social
I hack CSS: W3C CSSWG specwriter 2004– // Mozilla layout engine QA & coding 1999–2013
w3c.social
Happy New Year! This March marks 20 years since I joined the CSSWG officially. (!) I credit all my colleagues over the years for being so generally awesome that it’s hard to justify leaving. ;)
9
0
0