Closed Bug 1187748 Opened 9 years ago Closed 7 years ago

Allow web components within nested frames in certified apps

Categories

(Core :: DOM: Core & HTML, defect)

Product:
Core
Component:
DOM: Core & HTML
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: kgrandon, Assigned: wchen)

References

Details

We have a few additional places in gaia where we would like to be able to use web components. Generally this is all content we control, so we would like to enable web components for these additional cases. Right now it seems that web components do not work inside nested iframes in certified apps. We would like to enable web components for the following cases: <iframe certified app> <iframe http:// content> <- Allow web components here. </iframe> <iframe certified app> <iframe app:// (same origin)> <- Allow web components here. </iframe>
Jonas, William - Please weigh in if this is something we can do, and if it is a change we we are comfortable making for FxOS 2.5. Thanks!
Flags: needinfo?(wchen)
Flags: needinfo?(jonas)
Why would we allow use of web components in <iframe certified app> <iframe http:// content> <- Allow web components here. </iframe> case? I'd expect it would even break some things, since I assume certain web sites rely on the Chrome style web components (or if that is not available, use some script library). Gecko's web components isn't always compatible with the one in Chrome, and neither is at all compatible with what the specs will look like.
Did you mean <iframe certified app> <iframe app:// (same origin)> <- Allow web components here. </iframe>
Yes.. I wish I could edit past comments! (In reply to Olli Pettay [:smaug] (away-ish until July 26, expect slower than usual reviews) from comment #2) > Why would we allow use of web components in > <iframe certified app> > <iframe http:// content> <- Allow web components here. > </iframe> > case? At first I thought that this was needed for Firefox Accounts code, but it does seem that it's served from the same origin as the system app. We do have some code which is served from Mozilla servers, but that stuff is probably much lesser priority. I think only handling the same origin case for now should be fine. So to clarify, we only need to handle this for the time being: <iframe certified app> <iframe app:// (same origin)> <- Allow web components here. </iframe>
For the case when a certified app opens an iframe to itself, I.e. a same-origin iframe, I would think that you can already use webcomponents. Is that not the case?
Flags: needinfo?(jonas)
(In reply to Jonas Sicking (:sicking) from comment #6) > For the case when a certified app opens an iframe to itself, I.e. a > same-origin iframe, I would think that you can already use webcomponents. Is > that not the case? It seems to not work for me.
That indeed seems like a bug. I don't see a reason to apply different policies inside of a *same-origin* iframe.
William told me this is "just something that needs to be done" :)
Assignee: nobody → wchen
Flags: needinfo?(wchen)
No more certified apps.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.