- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Tue, 31 Mar 2026 20:15:40 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-sizing][responsive-frame] Should `frame-sizing` apply to `<object>` elements?``, and agreed to the following: * `RESOLVED: frame-sizing doesn't apply to <object> / <embed>` <details><summary>The full IRC log of that discussion</summary> <emilio> koji: so the other issue is whether it should apply on `<object>` / `<embed>`. For now we want to apply only to `<iframe>`<br> <emilio> q+<br> <emilio> Rossen: HTML seems to trend in that direction<br> <Rossen> ack emilio<br> <TabAtkins> emilio: seems fine, but can you remind me... is it frame-sizing: content?<br> <TabAtkins> TabAtkins: something liek that<br> <TabAtkins> emilio: i guess it's not a big issue to add object in the future, or do frame-sizing:none on an object/embed with SVG...<br> <TabAtkins> emilio: so should the initial value be 'auto'? so we can make 'none' work in the future?<br> <TabAtkins> emilio: 'auto' just seems more future proof<br> <TabAtkins> fantasai: i think since it's the initial value we can probably swap it in or out<br> <emilio> fantasai: we can probably swap the initial value in or out<br> <emilio> koji: there's an issue about auto from the january f2g<br> <iank_> https://drafts.csswg.org/css-sizing-4/#responsive-iframes<br> <emilio> f2f*<br> <koji> https://drafts.csswg.org/css-sizing-4/#responsive-iframes<br> <Rossen> Jan 27: RESOLVED: Define frame-sizing with various height and with keywords, with default of auto<br> <TabAtkins> (initial value is 'auto', there isn't a 'none' value at all yet)<br> <TabAtkins> emilio: okay, so if we want to add 'none' in the future that'll be safe<br> <emilio> PROPOSED: frame-sizing doesn't apply to <object> / <embed><br> <emilio> RESOLVED: frame-sizing doesn't apply to <object> / <embed><br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13584#issuecomment-4165224511 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 31 March 2026 20:15:40 UTC