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:
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 - w3.org/TR/RangeRequest/#timetogiveinput
This award recognizes the work done for: "Standardization of Font Technology for Custom Downloadable Fonts and Typography for Web and TV Devices": theemmys.tv/tech-73rd-award-…
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 👏👏👏
This is particularly useful for languages where fonts need to cover a very wide range of characters - typically when an ideographic writing system is used (e.g. in Chinese and Japanese) - downloading a multi-mega bytes font for a page makes downloadable fonts unpractical.
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 - w3.org/TR/RangeRequest/#timetogiveinput
If you're experimenting with Priority Hints, make sure to provide feedback (should get survey requests or send it to me directly). If you're holding back until it ships for realz, it won't unless enough devs try it out.
If you're not experimenting - why not and can I help?
#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. w3.org/TR/css-cascade-5/
Watch this🎬from @TerribleMia of the @csswg: youtube.com/vK8vj1l_oRk
#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.
w3.org/TR/css-cascade-4/
#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. w3.org/TR/css-conditional-3/
All current #CSS specs have their own specific levels ranging from 1 to 5, but CSS as a whole does not have a version. Two reasons: 1) some features are easier to complete than others, 2) CSS became so big that it is too much work for the editors to maintain as a monolithic spec.
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
📢 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! 👇
#CSS Cascading and Inheritance Level 6 explores another way of grouping style rules: the ‘scope’. An old idea, but which poses lots of questions w3.org/TR/css-cascade-6/
#CSS Conditional Rules Module Level 5 includes and extends the functionality of CSS Conditional 4, adding the rules ‘@when’ and ‘@else’, as well as introducing font processing queries to the supports query syntax used in ‘@supports’ rules w3.org/TR/css-conditional-5/
#CSS Containment Level 3 proposes to speed up rendering with ‘containment queries’: applying style rules only if an element has a certain size or other characteristic (like ‘media queries’ do for whole documents) w3.org/TR/css-contain-3/
All current #CSS specs have their own specific levels ranging from 1 to 5, but CSS as a whole does not have a version. Two reasons: 1) some features are easier to complete than others, 2) CSS became so big that it is too much work for the editors to maintain as a monolithic spec.