- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Thu, 13 Nov 2025 01:33:19 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-fonts-5] Text Fitting: Scaling of things based on font-size`, and agreed to the following: * `RESOLVED: start only with B, only text is scaled` <details><summary>The full IRC log of that discussion</summary> <ydaniv> tkent: this issue is about how other items align<br> <ydaniv> ... we had 3 options: A: all font-relative values are scaled based on font size<br> <kizu> q+<br> <astearns> q+<br> <ydaniv> ... b: nothing other than text should be scaled<br> <ydaniv> ... C: evenrhing should be scaled<br> <ydaniv> ... [shows example in slide]<br> <ydaniv> ... seems complexity is high when used with calc()<br> <ydaniv> ... (regarding to option A_<br> <TabAtkins> q+<br> <ydaniv> ... B is simple and we can extend later<br> <emilio> q+<br> <ydaniv> ... current impl. in Chrome is based on this<br> <kbabbitt> q+<br> <ydaniv> ... downside is non-text items can't be scaled<br> <ydaniv> ... [shows example in slides]<br> <ydaniv> q+<br> <ydaniv> ... in option A padding is re-evaluted<br> <florian> q+<br> <ydaniv> ... [missed]<br> <astearns> ack kizu<br> <ydaniv> kizu: I wanted to say there's discussion in the issue<br> <ydaniv> ... Chrome implemented B, works well, the main issue was that I wanted to have option A, don't think it's posisble but would like it<br> <ydaniv> ... don't think we should be limitting to one option<br> <ydaniv> ... also lea mentioned we may want other properties to fit/scale<br> <ydaniv> ... A and B could work in theory, we could implement A later<br> <ydaniv> ... if we would be able to do it later, we could fix later things that depend on font-size<br> <ydaniv> ... you could scale everything as much and later adjust other things accordingly<br> <ydaniv> ... you could mix and match all things<br> <ydaniv> ... think that combinations of other things should go to separate issue and we should consider them<br> <ydaniv> ... could be something like text-fit [missed]<br> <ydaniv> ... we don't yet what would be good by default<br> <ydaniv> ... we should start with option B and later continue on A<br> <ydaniv> astearns: on your last point, we don't have an explicit keyword for a default value<br> <ydaniv> ... I'd like to have an omittable dafault like auto<br> <ydaniv> ... in favor of doing B for now, even though A is cool<br> <ydaniv> ... worried that the scaling factor is available to authors<br> <ydaniv> ... some non-text thing that could scale on the line, and have no way of finding out what that was<br> <astearns> ack astearns<br> <astearns> ack TabAtkins<br> <ydaniv> TabAtkins: similar to what astearns said, this has been done before, don't want to do A until we have some ways to solve it<br> <astearns> s/factor is available/factor is not available/<br> <ydaniv> ... I think there are good use-cases for B, like if your text has an inline image, it sould scale the same way<br> <astearns> ack emilio<br> <ydaniv> ... happy with starting with B as default, and have some keyword to allowing it, and later pusure A<br> <ydaniv> emilio: I guess sum() does something similar<br> <ydaniv> s/sum()/zoom/<br> <noamr> -q+<br> <astearns> s/we don't have an explicit/we don't have to have an explicit/<br> <ydaniv> ... is there a 4th option for doing a slightly better behavior?<br> <astearns> ack kbabbitt<br> <ydaniv> kbabbitt: I understand C is stay simple, B is just simple zoom of the text?<br> <noamr> q-<br> <ydaniv> iank_: it's not just zoom text, you're changing font-size , not just scale<br> <ydaniv> kbabbitt: so you're basically changing font-size<br> <ydaniv> iank_ :just for text<br> <ydaniv> kbabbitt: was wondering how would that work with text-decorations<br> <astearns> ack ydaniv<br> <TabAtkins> ydaniv: was wondering; I wasn't able to catch up with everything while scribing<br> <TabAtkins> ydaniv: does this work with SVG text?<br> <TabAtkins> ydaniv: that' snot just a text node<br> <TabAtkins> astearns: I think that should be a separate issue that we consider<br> <astearns> ack florian<br> <ydaniv> florian: I think we have to go with B<br> <ydaniv> ... taht said, there are non-simple things we want to do, but not necessarily bound to A<br> <ydaniv> ... proabbly should also work with units<br> <ydaniv> ... but maybe be able to opt-in to other systems, like to grow into something, like the box decorations<br> <astearns> treat-image-as-text generic feature?<br> <ydaniv> ... currently only B makes sense for now<br> <ydaniv> fantasai: strongly thins shouldn't go into style computation, like A describes<br> <ydaniv> ... the ablilty to scale and change font-size are both useful, but they are different<br> <ydaniv> ... want to remind that for other stuff like letter spacing, we have a sizing option that allows changing other stuff<br> <ydaniv> ... there are a number of places in text layout where we previously relied only on em's and they resolve later and we needed percentage to do that<br> <ydaniv> ... makes sense to me to use zoom<br> <ydaniv> astearns: just to clarify, you're saying let's not do A for em's, but we have to do A for %'s?<br> <ydaniv> fantasai: it could because it's based on a used-time operation<br> <ydaniv> TabAtkins: the way we do it now is do a one-shot guess, and later scale to fit<br> <ydaniv> ... in that case we would not have an accurate font-size necessarily<br> <ydaniv> fantasai: you could adjust decorations to that<br> <kizu> q+<br> <ydaniv> astearns: I think this would not be effective for authors who wouldn't know what that scale was<br> <astearns> ack fantasai<br> <ydaniv> fantasai: if you're zooming text and doubling the size of font, and don't scale the letter spacing with it, it would be very weird<br> <schenney> Also text-decoration-thickness: from-font;<br> <ydaniv> ... if it's set in %'s it supposed to match font-size<br> <ydaniv> kizu: doing with one-shot as now and later apply fitting and scaling, as browsers currently apply<br> <ydaniv> ... maybe we could later add a second shot<br> <ydaniv> ... maybe what fantasai said could also work<br> <ydaniv> astearns: one min before break<br> <iank_> for the 2-shot TBH i don't think its worth it, but it should be another issue.<br> <ydaniv> florian: maybe separate to 2 issues, we could do with B and check what it applies to<br> <ydaniv> ... maybe would be harder to guess what your sclae would be in a one-shot<br> <TabAtkins> +1 to florian<br> <ydaniv> ... the auto default should deal with text and we need to explore and it should include letter-spacing<br> <ydaniv> PROPOSED RESOLUTION: start only with B, only text is scaled<br> <ydaniv> astearns: any objections?<br> <ydaniv> RESOLVED: start only with B, only text is scaled<br> <fantasai> s/is scaled/is scaled, "what is text" TBD/<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12888#issuecomment-3524706648 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 13 November 2025 01:33:19 UTC