Closed
Bug 570971
Opened 15 years ago
Closed 15 years ago
[e10s] local and remote browser bindings must both use message-based webProgress
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mfinkle, Unassigned)
Details
Attachments
(1 obsolete file)
Since we want to support both remote and local browser content with the same front-end code, we need to use the same webProgress methods and signatures.
This patch adds support to the local-browser binding for full webProgress support. It also updates the front-end code to use the message-based version of webprogress.
Also, the patch changes to use sendSyncMessage for bindings/browser.js message-based APIs because we were having lots of tests failing due to timing issues.
Lastly, it fixes a small loading issue in the viewport tests.
All tests pass with this patch.
Attachment #450123 -
Flags: review?(21)
|
Reporter | |
Comment 1•15 years ago
|
||
Comment on attachment 450123 [details] [diff] [review]
patch
No longer needed
Attachment #450123 -
Attachment is obsolete: true
Attachment #450123 -
Flags: review?(21)
|
|
Reporter | |
Comment 2•15 years ago
|
||
Fixed by bug 570969
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•