W3C home > Mailing lists > Public > public-css-archive@w3.org > February 2019

Re: [csswg-drafts] [css-inline] Should first/last baseline values of `vertical-align` belong to `alignment-baseline` or separate longhand? (#861)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 27 Feb 2019 21:53:55 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-468045924-1551304433-sysbot+gh@w3.org>
The CSS Working Group just discussed `aspect-ratio and width/height attributes`, and agreed to the following:

* `RESOLVED: we'll add a separate property for this`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: aspect-ratio and width/height attributes<br>
&lt;argyle> elika not you<br>
&lt;fantasai> ScribeNick: argyle<br>
&lt;argyle> there we go<br>
&lt;argyle> florian: my understandin as that we all agreed this would be a goo didea if possible, and we should check if possible<br>
&lt;argyle> tab disagrees, i want to hear that<br>
&lt;argyle> for context: "it" is using the width and height of attribtues to trigger the intrinsic aspect ratio<br>
&lt;argyle> elika: specifically, where we map the width and height to width and height props, we could also use them to calc the ratio back to css<br>
&lt;cbiesinger> s/elika/fantasai/<br>
&lt;argyle> that would solve the problem around the aspect ratio information would be lost due to waiting for the image to load, waiting to discover auto sizing<br>
&lt;AmeliaBR> s/that/...that/<br>
&lt;argyle> so the proposal was to introduce attributes to solve the same problem<br>
&lt;argyle> rosson: was is the data we need to gather then<br>
&lt;fantasai> s/was to introduce/was to do that instead of introducing new/<br>
&lt;argyle> florian: so we dont break the web<br>
&lt;AmeliaBR> s/so the/...so the/<br>
&lt;argyle> rossen: for the width and height<br>
&lt;argyle> florian: do we not agree?<br>
&lt;Rossen> s/rossen/Rossen/<br>
&lt;argyle> tab: having width and height be presentation attributes, and no affecting those new and exciting ways<br>
&lt;Rossen> s/tab/TabAtkins/<br>
&lt;argyle> tab: the other reason i liked it, some of the other things, like picture, you wanted to give an intrinsic size to them, and tab feels semantically better to be specific about being intrinsic than doing css things that also set intrinsic sizes.<br>
&lt;argyle> florian: there's no intrinsic tools to do this<br>
&lt;AmeliaBR> +1 to Tab's argument about `&lt;picture>&lt;source intrinsicsize="...">` making more sense than width &amp; height<br>
&lt;argyle> miles: what about canvas<br>
&lt;argyle> miles: we should consider the interaction with canvas where w and h have other meanings other than mapping to css<br>
&lt;cbiesinger> s/miles/myles/<br>
&lt;Rossen> q?<br>
&lt;Rossen> ack dbaron<br>
&lt;argyle> rosson: david, you're on the queue<br>
&lt;fantasai> s/miles/myles/<br>
&lt;fantasai> TabAtkins: It sets the backing store on width/height, which is compatible<br>
&lt;argyle> david: ... if this is a, major thing sites can do to improve loading, if a cms can just do this, that's great, and it means that lots of sites can get it cheaply<br>
&lt;argyle> david: i think, if it's it's won attr() it can do that, i dont think we ..<br>
&lt;fantasai> s/won attr()/own attribute/<br>
&lt;fantasai> s/i dont think we/I don't think it's as safe to do if we're re-using width and height/<br>
&lt;argyle> florian: if the cms wanted to check if there was previously a width and ehight, they could still inject the w/h and multiply by whats needed, but they also need to check minheight and maxheight, and then it gets messy<br>
&lt;argyle> alan: we're theorizing about things Ojan has experience in, at the most this conversation should inform what he continues to do as he tries to find a solution<br>
&lt;Rossen> q?<br>
&lt;argyle> alan: but i'm not sure i see the utility of theorizing when we have an experimentor<br>
&lt;argyle> florian: utility is we dont need to experiment if we have other demos, not worth checking if we dont want to do it anyway<br>
&lt;xfq> ack jen<br>
&lt;argyle> rosson: go ahead jenn<br>
&lt;cbiesinger> s/rosson/rossen/<br>
&lt;argyle> jenn: i think the original intention behind what elika was saying, here's an idea, might be much simpler than adding attributes, we'd like this considered<br>
&lt;TabAtkins> `&lt;style>img { width: 100%; }&lt;/style> &lt;img intrinsicsize="350x450">` works by default.  Changing it to &lt;img width=350 height=450> doesn't work; you have to manually set `height: auto` in CSS too.<br>
&lt;argyle> jenn: i do think there's a way to do it that hooks into cms's and existing things, instead of making it more complicated<br>
&lt;astearns> s/jenn/jensimmons_ /<br>
&lt;skk> s/alan/astearns/<br>
&lt;argyle> jenn: if only width is coming out of a cms, and there's no height, there's no mapping to intrinsic, we can map with that limited data<br>
&lt;argyle> jenn: maybe there's something more complex needed, and we do both, i think there's an elegance here tapping into what we already have. perhaps that's what ojan is intending<br>
&lt;argyle> jenn: hey, we're going to solve some of this in css, and to have that really heard, .. that's what i'd like to see happen<br>
&lt;argyle> rosson: where does this leave us<br>
&lt;astearns> s/rosson/Rossen /<br>
&lt;argyle> jenn: sounds like someone's going to find something out<br>
&lt;argyle> (thanks for the correction y'all!)<br>
&lt;argyle> (thanks for the corrections y'all!)<br>
&lt;argyle> amelia: i think it's great, we're leveraging something that already works, but i think i agree with the arguments there's too many cases where things can get messy for repurposing<br>
&lt;argyle> amelia: if browsers implemented the attr function that values to lengths, ... any image, grab these values, put them together, here's the ratio<br>
&lt;argyle> amelia: not sure if there's utility if no one's has implemented it yet<br>
&lt;jensimmons_> +1 to what AmeliaBR just said<br>
&lt;jensimmons_> maybe that could even be included in a project called CSS Remedy<br>
&lt;argyle> tab: i feel like there's just more discussion, but in the way of being explicit with cases and approaches, and i dont know if i want to spend time trying to nail it down<br>
&lt;argyle> elika: there are advantages of usign existing attr(), like for images out there, we get the faster layout/loading for free. info is already there<br>
&lt;argyle> no updating cms, no html file updates, it would let them hook into it via current functionality<br>
&lt;AmeliaBR> s/attr()/attributes/<br>
&lt;argyle> jenn: there's 100's of sites that put height and width on things. then in their code, height 100% in their code. decade of work built that way, and likely arent maintained<br>
&lt;fantasai> s/100's/100,000s/<br>
&lt;argyle> jenn: quick way to boost all sites<br>
&lt;astearns> s/on things/on images in the cms/<br>
&lt;argyle> jenn: don't get deep into picture element, ..., hey this is a performance thing, but it back in and it'll be faster<br>
&lt;argyle> jenn: other proposals will use it for be used for simple and complicated things, and some it'll be too much<br>
&lt;astearns> s/height 100%/width 100% height auto/<br>
&lt;argyle> elika: historically, we've asked users to put weight and height on them, back into the 90s, and hooking into that advice, it hooks into content and knowledge better. it wont just work on new things for people keeping up with latest things<br>
&lt;argyle> tab: happy to do more discussion, but not confident enough to decide now, or for us<br>
&lt;argyle> chris: maybe we could break out and talk about it?<br>
&lt;astearns> s/chris/chrishtr /<br>
&lt;argyle> chris: i dont think i fully understand, and I'd like time for that<br>
&lt;argyle> rossen: ok so, i didnt hear that say the HTML width and height attributes is the worst idea i've ever heard, we shouldnt do it<br>
&lt;argyle> rossen: i also didnt hear we shouldnt think about the intrinsic aspect ratio, because it'll just work<br>
&lt;argyle> rossen: tab has committed to work on this fully<br>
&lt;argyle> tab: chrome people will be working on this<br>
&lt;argyle> rossen: kidding aside, we'll close this issue for now. thanks for introducing it to the working group, and making it an actual proposal<br>
&lt;argyle> rossen: i think there was another bit in this, which was css property, which will then have to map using either the height or width attributes, as a ratio, or whatever else is there, if anything is added as an additional attribute<br>
&lt;argyle> rossen: i think the property can be discussed at a later point, or is this something you want to discuss later today<br>
&lt;argyle> elika: it's already in the draft<br>
&lt;fantasai> s/elika/fantasai/g<br>
&lt;argyle> jenn: so this discussion about not doing other things in HTML, the stuff we've already talked about, there will be more to talk about aspect ratio with min-height and min-width<br>
&lt;fantasai> s/jenn/jensimmons/g<br>
&lt;AmeliaBR> q+<br>
&lt;argyle> jenn: there is a question of: do we put in what's there already in the draft, support for ??, whether it's happening int he UA style sheet, we do have the ability to grab information about height and width<br>
&lt;argyle> jenn: might be right inbetween, and i think we should do what rossen mentioned<br>
&lt;argyle> rossen: great point, thank you. before we move on<br>
&lt;Rossen> ack AmeliaBR<br>
&lt;argyle> amelia: i have a question: it's not being proposed by a web group. before we get a css spec, we need to get that moving up into the HTML wg, so it's outside our scope, so long as it's going through process and getting standardized. chrome pushed it without standarization, we need to make sure that happens<br>
&lt;astearns> TabAtkins: definitely should be in wicg - we'll get it there<br>
&lt;argyle> rossen: topic, css inline, first and last baseline<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/861<br>
&lt;argyle> dauwhe: no opinions<br>
&lt;argyle> elika: this issue keeps coming up because i dont have any points in favor or against either options, and i'd like to hear why we should pick one over the other<br>
&lt;argyle> fantasai: do we have the board, do you want the [..] baselines, fantasai explains the problem<br>
&lt;argyle> fantasai: once you match the baselines, you shift<br>
&lt;argyle> fantasai: once one of those has multiple lines in it, what do we do<br>
&lt;argyle> fantasai: do we put it in it's own properly, align baseline preference, and it cascades independently, .. continues explaining<br>
&lt;argyle> AmeliaBR: reminder: long hands exist for legacy compat. so svg had align, baseline shift, css had vertical align.. they descirbe the same functionality but behave slightly differently<br>
&lt;argyle> AmeliaBR: ..., adding new features to the long hand, when it's just for compat, seems questionable. also, not sure how first/last would work in SVG. i dont see benefit there<br>
&lt;astearns> [fantasai outlines things on the easel]<br>
&lt;argyle> fantasai: we cant add values to the short. so it there's a reason to choose one over the other, it'll help us resolve<br>
&lt;argyle> AmeliaBR: new property may not be used<br>
&lt;argyle> fantasai: related issue: from the MATH ML folks, they want to take the baseline not from the first or last item, but from a specific item<br>
&lt;argyle> fantasai: so that ties in a little bit with this, we dont have a proposal, but we have an idea we should do it. so that might tie into we end up with another that helps us solve this as well<br>
&lt;argyle> AmeliaBR: i suppose the value of a new property is that vertical align is already supported with current functionality<br>
&lt;argyle> AmeliaBR: you may end up with duplication anyway<br>
&lt;argyle> fantasai: does anyone want to think about it more, or push it off to the next<br>
&lt;argyle> dbaron: i can imagine there's reasons you want them separate, unknown how important they are. consider multiple languages..<br>
&lt;argyle> fantasai: alright, we can resolve the issue<br>
&lt;argyle> dbaron: i'm not convinced anyone will want to do this, but it does seem like a good thing to do<br>
&lt;argyle> AmeliaBR: resolve to make a new long form property<br>
&lt;argyle> astearns: we figure the name out later<br>
&lt;argyle> fantasai: no matter how silly, make suggestions<br>
&lt;fantasai> s/suggestions/suggestions in IRC, we'll evaluate later/<br>
&lt;dbaron> dbaron (earlier): you might want to set alignment-baseline as a function of the language without messing with the first/last choice set for other reasons<br>
&lt;argyle> Rossen: ok, any other opinions that can top David Barons?<br>
&lt;argyle> Rossen: anyone object to david? or oppose?<br>
&lt;argyle> Rossen: no objections. resolved.<br>
&lt;argyle> astearns: so, david, could you put your actual suggestion into resolve line<br>
&lt;argyle> dbaron: the question was a boolean, do we want a separate prop or not<br>
&lt;argyle> RESOLVED: we'll add a separate property for this<br>
&lt;argyle> astearns: great<br>
&lt;argyle> fantasai: thank you<br>
&lt;argyle> Rossen: next one is an awesome one<br>
&lt;emilio> ScribeNick: emilio<br>
&lt;florian> github: none<br>
&lt;Rossen> github: https://github.com/w3c/csswg-drafts/issues/861<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/861#issuecomment-468045924 using your GitHub account
Received on Wednesday, 27 February 2019 21:53:56 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:44 UTC