201 Followers
11 Following
26 Posts
I hack CSS: W3C CSSWG specwriter 2004– // Mozilla layout engine QA & coding 1999–2013
@SaraSoueidan Sorry! Didn't see this cuz I don't log in very often. I think that's a good question for @flackr

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".

@johannes Oh, please please please add some of your specific use cases/examples into the issue! That would help a lot!

Me entering my number in a form field: *enters 3 numbers*

Form field: NO NO, that's an invalid phone number

Me: *enters the next three numbers*

Form field: what the hell? NO, this is invalid

Me: *finishes the last four numbers*

Form field: Ohhh I get it now! Yeah that's valid

Cascading Style Sheets, level 1

QOTD: “If you don’t tackle the hard questions at dinner time, when are you going to solve them?”
@bole @jensimmons Safari now supports percentages for letter-spacing and word-spacing, fwiw.
@tigt @jensimmons Can you describe that more?
CSS Fonts Module Level 4

@benetherington @jensimmons That ... should work. Can you send me a testcase?

Note: if it's an inline block, though, for compat reasons, it's always breakable before/after. We're discussing a switch in https://github.com/w3c/csswg-drafts/issues/4949 ...

[css-text-3] Switch line-breaking handling of atomic inlines · Issue #4949 · w3c/csswg-drafts

CSS Text tried to define that atomic inlines behave like ID characters with respect to line breaking (e.g., breaks between an atomic inline and a closing parenthesis or comma is forbidden). We had ...

GitHub