Cross-process iframes are blank
Bug #1631450 reported by
Chris Coulson
on 2016-10-07
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| Oxide |
High
|
Chris Coulson |
Bug Description
- Launch webbrowser-app with OXIDE_PROCESS_
- Navigate to http://
- Click on one of the "Go cross-site.." buttons.
Notice that the iframe appears to be blank, but it works in Chromium and without OXIDE_PROCESS_MODEL set.
Related branches
Chris Coulson (chrisccoulson)
on 2016-10-07
Changed in oxide: | |
importance: | Undecided → High |
status: | New → Triaged |
summary: |
- Cross-process iframes with OXIDE_PROCESS_MODE=site-per-process are blank + Cross-process iframes with OXIDE_PROCESS_MODEL=site-per-process are + blank |
Chris Coulson (chrisccoulson) wrote : Re: Cross-process iframes with OXIDE_PROCESS_MODEL=site-per-process are blank | #1 |
Chris Coulson (chrisccoulson)
on 2016-10-07
summary: |
- Cross-process iframes with OXIDE_PROCESS_MODEL=site-per-process are - blank + Cross-process iframes are blank |
Chris Coulson (chrisccoulson) wrote : | #2 |
Changed in oxide: | |
status: | Triaged → Fix Released |
assignee: | nobody → Chris Coulson (chrisccoulson) |
milestone: | none → branch-1.19 |
To post a comment you must log in.
I believe this is because Oxide's RWHV and Chromium's RWHVChildFrame aren't sharing a cc::SurfaceManager. Also, we don't implement RWHV::GetSurfac eClientId (which is now RWHV::GetFrameS inkId in Chromium trunk)