We're Cascading with Style... https://nitter.cf/t.co/3QCqdWw9pW
worldwide
Joined March 2008
- Tweets1.8K
- Following56
- Followers43.3K
- Likes131
CSS Working Group retweeted
At the @CSSWG group meeting today, I presented some new ideas from Apple about how Anchor Positioning could work.
Slides are here. Use the "Menu" UI at the top left to show speaker notes and see what we said as we presented:
icloud.com/keynote/0f5Uxcimb…
CSS Working Group retweeted
I'm curious of people's thoughts on this new approach
At the @CSSWG group meeting today, I presented some new ideas from Apple about how Anchor Positioning could work.
Slides are here. Use the "Menu" UI at the top left to show speaker notes and see what we said as we presented:
icloud.com/keynote/0f5Uxcimb…
CSS Working Group retweeted
Which of the following best expresses how you want to write nested CSS when it's implemented by browsers?
A. I want to use & in every selector, as I think it makes code more clear
B. I want to be able to omit & whenever possible, as it's noisy to read and a hassle to type
44%A
40%B
17%🤷🏽♀️ Just show results
1,613 votes • Final results CSS Working Group retweeted
2021 was another super productive year for @csswg in benefit to our global society! We closed 636 GitHub issues and published 1 FPWD, 17 Working Drafts, 4 Candidate Recommendations, 6 CR Drafts, and 2 Recommendations. Congrats and Thank You!!
CSS Working Group retweeted
New working draft of CSS Color 5 also published today
w3.org/TR/2021/WD-css-color-…
@csswg @w3c color mixing, modification, contrast checking
CSS Working Group retweeted
New working draft of CSS Color 4 published today
w3.org/TR/2021/WD-css-color-…
@csswg @w3c lots of updates!
CSS Working Group retweeted
What do you not understand about CSS? Not the things you find hard to remember, but what things about the language or decisions made by spec authors do you find baffling?
CSS Working Group retweeted
Also @fantasai notes that: the focus on submitting a PR to change a spec is neglecting a more important step that should come first: discussing the issue and getting agreement. The editor can make the actual change to the spec; contributors don't have to.
CSS Working Group retweeted
The first level of design is to make sure you have the right semantic HTML (so your content works as audio, in Reader mode, in screen readers, highly constrained devices, search engines, and more). @jensimmons #AEACHI
CSS Working Group retweeted
Note that "has correct orientation" can be checked by opening the image in pretty much any normal photo editor. If it looks good, it'll be fine. If it's rotated weirdly, you might have a problem and need to fix it in a decent image editor.
CSS Working Group retweeted
Confused about how line-wrapping works in CSS? @frivoal clears it up here:
CSS Working Group retweeted
Don't use font-feature-settings directly if you can avoid it; use the more specialized property for the feature instead.
In this case, `font-variant-numeric: tabular-nums` does the job (and gives a lot more options too!).
drafts.csswg.org/css-fonts/#…
This quoted post is unavailable.
CSS Working Group retweeted
This might be good time to reiterate why independent implementations, both at a high-level (e.g., browser) and low-level (e.g., text encodings) are valued and important to a healthy and thriving web platform. (And please do feel free to chime in and discuss.)
CSS Working Group retweeted
I wrote about the things we discussed in the CSS WG at TPAC last week smashingmagazine.com/2018/10… #webdirections #wds18
CSS Working Group retweeted
I'm working on specifying the default rendering of form controls and the -webkit-appearance property. Let me know your pain points wrt styling form controls, I can try to fix it.
