BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20260219T073616Z
BEGIN:VTIMEZONE
TZID:Asia/Tokyo
X-MICROSOFT-CDO-TZID:20
BEGIN:STANDARD
DTSTART:20241115T080000
TZOFFSETFROM:+0900
TZOFFSETTO:+0900
TZNAME:JST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:f5bc8948-a0d0-4d95-9f89-b29dfbff62fa
DTSTAMP:20260219T073616Z
SUMMARY:Find deterministic sizing rules for free-form documents
DTSTART;TZID=Asia/Tokyo:20251110T170000
DTEND;TZID=Asia/Tokyo:20251110T180000
DESCRIPTION:https://www.w3.org/events/meetings/f5bc8948-a0d0-4d95-9f89-b29d
 fbff62fa/\n\nHistorically\, the viewport of html documents has always been
  determined by the browsers frame\, being the browser window\, browser tab
 \, or browser popup size. The author of the html document can then base th
 eir own styling and dimensions based on this size with units like vw and v
 h which in these situations are deterministic and non-ambiguous.\n\nWith t
 he introduction of web extensions\, a new type of situation is born in whi
 ch the author of the html document can\, with certain restraints and many 
 issues (which you can read about below) determine and change the size of t
 he viewport by changing the height/width of the html/body elements. Exampl
 es are the extension popup and the options page if defined with options_ui
 .open_in_tab=false.\n\nIn an ideal world the document would communicate (i
 n any form\, declarative in css for example) its preferred min/ideal/max h
 eight/width if in auto size. In which the ideal height/width could also me
 an "match" the browsers ideal sizing if it sits in between the min/max ran
 ge. This preference is then incorporated by the browser and either fully o
 r partially respected to render the auto-sized content.\n\nThere is some p
 rior art in the CSSWG which discusses the auto-sizing of iframe elements o
 n their parent document. See:\nhttps://github.com/w3c/csswg-drafts/issues/
 1771 and https://github.com/domenic/cooperatively-sized-iframes\nand in th
 e WECG:\nhttps://github.com/w3c/webextensions/issues/692 and https://githu
 b.com/w3c/webextensions/issues/436\n\nSome of the techniques currently in 
 use for the auto sizing and some of the proposals to accompany them can be
  reused/shared for auto-sizing of iframes.\n\nWith iframes\, security is a
  concern so the auto-sizing can not be opt-in by default for both host and
  iframe. A potential way to address this would be adding a "autosize" keyw
 ord to the <meta name="viewport"> and an autosize attribute on the iframe.
 \n\n**Goal(s):**\nBrainstorm about potential solutions and reduce the scop
 e of solutions to determine next steps.\n\nAgenda\n\n**Materials:**\n- [Se
 ssion proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/issues
 /58)
STATUS:CONFIRMED
CREATED:20251028T131432Z
LAST-MODIFIED:20260219T073616Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Floor 4 - 406
CATEGORIES:TPAC 2025,Breakout Sessions
END:VEVENT
END:VCALENDAR