New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[css-env] safe-area-insets-* for embedded document by iframe #4670
Comments
... and should they change based on where the iframe is? |
No, that sounds like a straight-forward cross-origin information leak. |
Yes, that sounds like a cross-origin information leak, but I can imagine that there are use cases for that. For example, certain site may want to have an iframe taking the whole viewport and interact with it somehow. I'm thinking that maybe the parent document should be able to control the Since environment variables are currently only exposed via CSS, it would probably be a good idea to also do such control via CSS, for example, maybe we can provide a set of properties for iframe just following the same names as the environment variables, and the value would be applied into the iframe for them. WDYT? |
Seems like that could be used as a somewhat-sophisticated postMessage... Not sure, it seems nice and there are other use-cases for such things, but a bit scared about the implications of the receiver of the properties being able to run script to read them and react to them... Anyhow if we go that route we should probably expose them for svg images and such first, rather than iframes... |
The CSS Working Group just discussed The full IRC log of that discussion<TabAtkins> Topic: safe-area-insets<RossenF2F> github:https://github.com//issues/4670 <TabAtkins> emilio: there's no explicit area in env() spec about how safe-area-inset behaves in iframes <TabAtkins> emilio: ipmls disagree. We're doing some related work, would like it clarified. <TabAtkins> emilio: If iframes are nested, they may not care about safe areas, etc. <TabAtkins> TabAtkins: Who's responsible for this spec? <TabAtkins> heycam: dino and you <TabAtkins> TabAtkins: I'm there for processing model, not values. ^_^ <RossenF2F> Zakim, open queue <Zakim> ok, RossenF2F, the speaker queue is open <TabAtkins> hober: I'm happy to bug dean about this. <TabAtkins> TabAtkins: Can you (emilio) tag dino into the thread? <TabAtkins> emilio: Yes |
CC @grorg, maybe you could weigh-in? |
Since safe area insets uses on content, we need send it from chrome process to content process. SafeAreaInsetsChanged will be called per window position/size change (Next patch is Android implementation for it), we have to calculate safe area insets on widget/window per change. Current implementation is that this value is top level document only like Blink since w3c/csswg-drafts#4670 isn't resolved yet. Differential Revision: https://phabricator.services.mozilla.com/D55084
Since safe area insets uses on content, we need send it from chrome process to content process. SafeAreaInsetsChanged will be called per window position/size change (Next patch is Android implementation for it), we have to calculate safe area insets on widget/window per change. Current implementation is that this value is top level document only like Blink since w3c/csswg-drafts#4670 isn't resolved yet. Differential Revision: https://phabricator.services.mozilla.com/D55084
Since safe area insets uses on content, we need send it from chrome process to content process. SafeAreaInsetsChanged will be called per window position/size change (Next patch is Android implementation for it), we have to calculate safe area insets on widget/window per change. Current implementation is that this value is top level document only like Blink since w3c/csswg-drafts#4670 isn't resolved yet. Differential Revision: https://phabricator.services.mozilla.com/D55084 --HG-- extra : moz-landing-system : lando
Since safe area insets uses on content, we need send it from chrome process to content process. SafeAreaInsetsChanged will be called per window position/size change (Next patch is Android implementation for it), we have to calculate safe area insets on widget/window per change. Current implementation is that this value is top level document only like Blink since w3c/csswg-drafts#4670 isn't resolved yet. Differential Revision: https://phabricator.services.mozilla.com/D55084 --HG-- extra : moz-landing-system : lando
Since safe area insets uses on content, we need send it from chrome process to content process. SafeAreaInsetsChanged will be called per window position/size change (Next patch is Android implementation for it), we have to calculate safe area insets on widget/window per change. Current implementation is that this value is top level document only like Blink since w3c/csswg-drafts#4670 isn't resolved yet. Differential Revision: https://phabricator.services.mozilla.com/D55084 UltraBlame original commit: 43fdc889beacab5c72dd48a66aae47f25d95b5e0
Since safe area insets uses on content, we need send it from chrome process to content process. SafeAreaInsetsChanged will be called per window position/size change (Next patch is Android implementation for it), we have to calculate safe area insets on widget/window per change. Current implementation is that this value is top level document only like Blink since w3c/csswg-drafts#4670 isn't resolved yet. Differential Revision: https://phabricator.services.mozilla.com/D55084 UltraBlame original commit: d155d510d1a19c3be047dedd63f52562de6a980b
Since safe area insets uses on content, we need send it from chrome process to content process. SafeAreaInsetsChanged will be called per window position/size change (Next patch is Android implementation for it), we have to calculate safe area insets on widget/window per change. Current implementation is that this value is top level document only like Blink since w3c/csswg-drafts#4670 isn't resolved yet. Differential Revision: https://phabricator.services.mozilla.com/D55084 UltraBlame original commit: 43fdc889beacab5c72dd48a66aae47f25d95b5e0
Since safe area insets uses on content, we need send it from chrome process to content process. SafeAreaInsetsChanged will be called per window position/size change (Next patch is Android implementation for it), we have to calculate safe area insets on widget/window per change. Current implementation is that this value is top level document only like Blink since w3c/csswg-drafts#4670 isn't resolved yet. Differential Revision: https://phabricator.services.mozilla.com/D55084 UltraBlame original commit: d155d510d1a19c3be047dedd63f52562de6a980b
Since safe area insets uses on content, we need send it from chrome process to content process. SafeAreaInsetsChanged will be called per window position/size change (Next patch is Android implementation for it), we have to calculate safe area insets on widget/window per change. Current implementation is that this value is top level document only like Blink since w3c/csswg-drafts#4670 isn't resolved yet. Differential Revision: https://phabricator.services.mozilla.com/D55084 UltraBlame original commit: 43fdc889beacab5c72dd48a66aae47f25d95b5e0
Since safe area insets uses on content, we need send it from chrome process to content process. SafeAreaInsetsChanged will be called per window position/size change (Next patch is Android implementation for it), we have to calculate safe area insets on widget/window per change. Current implementation is that this value is top level document only like Blink since w3c/csswg-drafts#4670 isn't resolved yet. Differential Revision: https://phabricator.services.mozilla.com/D55084 UltraBlame original commit: d155d510d1a19c3be047dedd63f52562de6a980b
Also interested in an update here, especially to simulate devices with safe-area on desktop: cf storybookjs/storybook#12852 Being able to set env variables for an iframe would be a must ! |
safe-area-insets-*
is the defines for visible rectangle such as cutout support. But I guess that it is unclear for embedded document byiframe
.iframe
.What correct behaviour for embedded document?
parent
child / embedded document
The text was updated successfully, but these errors were encountered: