- From: Xidorn Quan via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Mar 2023 01:01:02 +0000
- To: public-css-archive@w3.org
I agree that conceptually it would be good for each frame to have its own visual viewport to indicate how it's scaled and presented, but in practice I'm not sure how useful it is. Parent document often wants the embedded content to look in a certain way, so it may be undesirable if user can change the viewport / zoom independently. Even if the parent document doesn't care, it might cause confusion for users if browser supports doing different zooming in different parts of the document. Given this, and the fact that no browser seemingly supports that, it might be good to revisit the choice. If the `scale` can be represented in a way that is independent to the document original dimensions, the scale would be purely from the user gesture, and the only thing it can possibly leak is the size of content on the page, which I doubt would be a useful side channel. OTOH, if we care about leaking size of content, this is already leaking content inside iframe to the parent document crossing the origin boundary, I don't see why the reverse would be a larger problem given parent document generally have more control over content inside iframe than the reverse. -- GitHub Notification of comment by upsuper Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8434#issuecomment-1457302235 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 7 March 2023 01:01:04 UTC