- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Dec 2021 01:00:27 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `layout of iframes`, and agreed to the following: * `RESOLVED: object-fit affects the rendering of iframes with expressed intrinsic sizes` * `RESOLVED: object-position applies to iframes in the above case as well` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> Topic: layout of iframes<br> <TabAtkins> github: https://github.com/w3c/csswg-drafts/issues/6817<br> <TabAtkins> chrishtr: About iframes with content size different from the iframe element<br> <TabAtkins> chrishtr: Currently not possible<br> <TabAtkins> chrishtr: But two upcoming features that might change this<br> <TabAtkins> chrishtr: fenced frame that prevents iframe content from changing size after laoded, to avoid info leaks<br> <TabAtkins> chrishtr: And cooperative iframe sizing, which may let the content document size differently from the iframe element<br> <TabAtkins> chrishtr: I propose we apply object-fit semantics to this, and default to object-fit: contain<br> <TabAtkins> chrishtr: (thus letterboxing the iframe)<br> <TabAtkins> fantasai: Does this mean you'll shrink/zoom out the iframe if it's smaller than the document?<br> <TabAtkins> chrishtr: Yes<br> <TabAtkins> chrishtr: I think that would look the best, if they differ.<br> <TabAtkins> smfr: not sure i agree - flashes of scaled content are weird<br> <TabAtkins> smfr: Could just attach it to start-start corner<br> <TabAtkins> chrishtr: so two potential resolutions: one is whether object-fit works, and second is what the default value is<br> <fantasai> TabAtkins: applying oject-fit makes sense, it's designed to handle this kind of thing<br> <fantasai> TabAtkins: no reason not to work as it does elsewhere<br> <fantasai> TabAtkins: no strong opinion about default value<br> <dholbert> q+<br> <fantasai> TabAtkins: if question between losing data because doing object-fit: none and overflowing in some way<br> <fantasai> TabAtkins: or making something very small, either squished or zoomed out<br> <fantasai> TabAtkins: they're both pretty bad<br> <fantasai> TabAtkins: I'm not sure which is best for the user<br> <TabAtkins> chrishtr: none would cut off content<br> <TabAtkins> chrishtr: there's also "smaller" - only transform if you have to make it smaller to fit<br> <TabAtkins> chrishtr: "scale-down"<br> <TabAtkins> smfr: Is this a frozen iframe?<br> <TabAtkins> chrishtr: For a fenced frame, this would persist for th elife of the frame - they'd interact with it potentially<br> <TabAtkins> chrishtr: These are for, like, ads - the 3rd party doesn't see what size the iframe ends up being<br> <TabAtkins> chrishtr: Authors should avoid having this happen, but when it does we need some dfn for the behavior<br> <TabAtkins> dholbert: This have any effect on regular iframes?<br> <fantasai> TabAtkins: no, they continue o have no intrinsic size and work as they do today<br> <TabAtkins> Rossen_: what's the scenaro?<br> <TabAtkins> dholbert: <iframe src="giant-image.jpg"><br> <TabAtkins> dholbert: Chrome displays at full res, Firefox does scaled down but you can click it to go full, unsure what webkit does<br> <TabAtkins> Rossen_: given we dont' have interop...<br> <TabAtkins> dholbert: Taht's what i'm getting at, does this have any effect on these<br> <TabAtkins> chrishtr: This shouldn't have any effect on today's iframes, only on the new stuff the cited proposals can bring up<br> <TabAtkins> chrishtr: Only situations where there is an expressed intrinsic sizing (iframes today don't have it at all) and there's a mismatch<br> <TabAtkins> Rossen_: Objections?<br> <fantasai> TabAtkins: Should we resolve separately on whether to apply the property and what the default shoul be?<br> <TabAtkins> RESOLVED: object-fit affects the rendering of iframes with expressed intrinsic sizes<br> <TabAtkins> chrishtr: I'd like the resolution for the second now, if possible<br> <TabAtkins> Rossen_: we can change in the future<br> <TabAtkins> dholbert: object-position should also be relevant<br> <TabAtkins> TabAtkins: oh yeah i assumed it would be<br> <TabAtkins> Rossen_: Objections?<br> <TabAtkins> RESOLVED: object-position applies to iframes in the above case as well<br> <TabAtkins> Rossen_: Please work out the defaults in the issue and we can resolve next week<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6817#issuecomment-984196258 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 December 2021 01:00:29 UTC