w3cdevs Twitter archive for January 2022

📢 While we're still in #NewYearResolutions period, which should the Web Platform take for #2022?
#Web #developers, please name bad habits to quit and/or good new behaviors to aspire to. Thanks! 👇

Today, we highlight the progress of three #CSS specifications on three levels: 3, 4 and 5! They are all in @w3c "Candidate Recommendation" status #timetoimplement https://twitter.com/w3c/status/1481527486659940353

As you know, a #CSS level is not a version. For ex., level 5 is everything from level 4 and a bit more. Read this short #explainer: https://twitter.com/w3cdevs/status/1234883952588075008

#CSS Conditional Rules Module Level 3: compared to level 2, the main extensions are allowing nesting of certain at-rules inside '@media', and the addition of the '@supports' rule for conditional processing. https://www.w3.org/TR/css-conditional-3/

#CSS Cascading and Inheritance Level 4 defines the basic rules of propagating style properties & values to all elements. Plus the 'all' property and the 'unset' and 'revert' keywords.
https://www.w3.org/TR/css-cascade-4/

Finally, remember that the @csswg publishes a list of stable modules to tell #implementors the current state of CSS, currently the "CSS Snapshot 2021": https://w3.org/TR/CSS/

#CSS Cascading and Inheritance Level 5 specifies everything from level 4, plus ‘layers’ that authors can create to represent element defaults, 3rd-party libraries, override styles, etc. https://www.w3.org/TR/css-cascade-5/
Watch this🎬from @TerribleMia of the @csswg: https://youtu.be/vK8vj1l_oRk

Priority Hints propose an HTML attribute (on embedded resources) and a parameter to @fetchstandard to prioritize the importance of a given HTTP request https://wicg.github.io/priority-hints/ #feedbackneeded https://twitter.com/patmeenan/status/1481416324857438208

Incremental #Font Transfer (IFT) via #HTTP range requests allows to load only the portions of a font necessary to display a page, and augment them as needed - https://www.w3.org/TR/RangeRequest/ #timetogiveinput https://twitter.com/w3c/status/1485896320917422082

This spec. complements IFT PatchRequest and is simpler to deploy - read what IFT is about: https://twitter.com/w3cdevs/status/1435183905150222339

Feedback and suggestions are welcomed on the #github repository: https://github.com/w3c/IFT/issues/

The @w3c #WebFonts #WorkingGroup got a #TechEmmy Award @TheEmmys! Congrats to chairs Vladimir Levantovsky and Garret Rieger + all the group's participants, and especially our own @svgeesus who has been a key driving force of this work since its inception 👏👏👏 https://twitter.com/w3c/status/1486475062182137859

This award recognizes the work done for: "Standardization of Font Technology for Custom Downloadable Fonts and Typography for Web and TV Devices": https://theemmys.tv/tech-73rd-award-recipients/

Read @svgeesus' reflections on the work done by the #WebFonts #WorkingGroup over the past 25 years: https://mobile.twitter.com/svgeesus/status/1486454562605129742

Font support and development continues as more work is needed to make Web fonts attractive for all world languages - the #WebFonts Working Group has recently asked for input for the Incremental #Font Transfer (IFT) specs: https://twitter.com/w3cdevs/status/1485931390579494915