Closed
Bug 1342010
Opened 7 years ago
Closed 7 years ago
LocalStorage changes handled by iframes in another tabs have delay.
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1285898
People
(Reporter: blazej.pichur, Unassigned)
Details
Attachments
(1 file)
1.16 KB,
application/gzip
|
Details |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0 Build ID: 20170201180315 Steps to reproduce: I have a simple add-on which have popup with embedded iframe and content script. Iframe is responsible for access to localStorage of src domain. In my example it is: http://example.com. Opening a popup in a different domain/tab should get me access to any value from http://example.com localStorage. The problem is when this value is changed by http://example.com I can see these changes after some delay in other tabs. I have used Firefox 53.0a2 Developer Edition for testing. I need match_about_blank behavior which is available only in this edition. 1. Load temporary add-on which is attached to this bug. 2. Open website: http://example.com 3. Open console and type: localStorage.setItem("something", "new value"); "something" as a key is important, because it is used in add-on code. 4. Open another tab and click extension's button. You can try these steps few times, because sometimes it works properly (rather rarely). Actual results: Text in popup isn't changed immediately. It takes about 30 seconds when after clicked the change occurs. Expected results: Text in popup should be changed immediately - localStorage events should be visible immediately in another tabs.
Component: Untriaged → WebExtensions: Untriaged
Product: Firefox → Toolkit
Updated•7 years ago
|
Component: WebExtensions: Untriaged → DOM
Product: Toolkit → Core
Comment 1•7 years ago
|
||
According to https://wiki.mozilla.org/E10s#Schedule, multiprocess e10s is enabled in Firefox 53 (Aurora/Dev edition), so this is likely to be bug 1285898 which is fixed in Firefox 54, which will imminently be Aurora per https://wiki.mozilla.org/RapidRelease/Calendar. So I expect this bug can be duped to bug 1285898. Specifically, the bug fix propagates localStorage changes between content processes and generates "storage" events.
Comment 2•7 years ago
|
||
Thanks Andrew for the response! Hi Błażej Pichur, thanks for reporting this. According to comment 1, I am going to close this as a duplicate. Please give it a try on FF 54. If you still see the issue, feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•