Closed
Bug 642658
Opened 15 years ago
Closed 15 years ago
Switch to postMessage for the page creation
Categories
(Cloud Services :: Share: Web Client, defect)
Cloud Services
Share: Web Client
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: formerly-j-r-burke, Assigned: formerly-j-r-burke)
References
Details
(Whiteboard: [eta needs addon support, 1 day])
Attachments
(1 file, 1 obsolete file)
Don't parse fragment ID, use postMessage, and remove the hashchange watcher.
![]() |
Assignee | |
Comment 1•15 years ago
|
||
Attachment #522828 -
Flags: review?(mixedpuppy)
Comment 2•15 years ago
|
||
This sends the share state to the panel on tab switch and on popupshowing
Attachment #522892 -
Flags: review?(philipp)
Comment 3•15 years ago
|
||
Comment on attachment 522828 [details]
Pointer to pull request
On the very first opening of the panel the web content no longer needs to fetch the share state. Upon acceptance of the panel patch also attached to this bug, the share state is always sent when switching tabs or opening the panel. Once I finish the patches up, I'll commit the small fix to this branch.
Attachment #522828 -
Flags: review?(mixedpuppy) → review-
Comment 4•15 years ago
|
||
Comment on attachment 522892 [details] [diff] [review]
patch to send share state to panel
I'm revoking this patch, it needs a couple more changes.
Attachment #522892 -
Flags: review?(philipp)
![]() |
Assignee | |
Comment 5•15 years ago
|
||
OK as long as the on first open the chrome sends the shareState message at the right time: it could be possible that the page takes a bit to load, or in the reopen case, after a day the web conent will reload itself, so I can see where it will need to expicitly ask the chrome for the shareState.
![]() |
||
Comment 6•15 years ago
|
||
Comment on attachment 522892 [details] [diff] [review]
patch to send share state to panel
This patch is also in the wrong bug. This bug is about the web client only. Bug 642655 deals with the chrome bits. (Just FYI when you have an updated patch.)
Attachment #522892 -
Attachment is obsolete: true
Comment 7•15 years ago
|
||
James, review the commit I did to the bug branch, and see bug 642655 for the chrome side of this. Then do a pull review again.
![]() |
Assignee | |
Comment 8•15 years ago
|
||
Comment on attachment 522828 [details]
Pointer to pull request
Seeing if I can reuse the existing attachment for review: looked at mixedpuppy's additional commit in the bug branch and looks good to me.
Attachment #522828 -
Flags: review- → review?(mixedpuppy)
Comment 9•15 years ago
|
||
Comment on attachment 522828 [details]
Pointer to pull request
do not merge this until bug 642655 is r+, they need to land together.
Attachment #522828 -
Flags: review?(mixedpuppy) → review+
![]() |
||
Comment 10•15 years ago
|
||
(In reply to comment #9)
> do not merge this until bug 642655 is r+, they need to land together.
Bug 642655 landed on fx-share, this can be merged now.
Comment 11•15 years ago
|
||
landed web content update
https://github.com/mozilla/f1/commit/87e5f645eb57d4ca4ad837b19cae3fbf31883ace
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
•