You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The iron-localstorage element handles the 'storage' event, which is fired when localStorage has been manipulated from another window. When localStorage.clear is called from another window, it clears all entries in the local storage and the 'storage' event is fired. iron-localstorage should be firing the iron-localstorage-load-empty event, but does not.
Expected outcome
'iron-localstorage-load-empty' should be fired when localStorage.clear is called from another window.
Actual outcome
'iron-localstorage-load-empty' isn't fired.
Live Demo
Steps to reproduce
Put an iron-localstorage element with a default value in the page.
echo the bound value on the page
Open the page in chrome.
Open up the Developer Tools
Go to Application and check the value is in the Local Storage
Go to Clear Storage section, and make sure 'Local and session storage' is checked and click 'Clear site data'. This fires the 'storage' event that iron-localstorage is listening for.
Since this event isn't handled, the bound value won't update
Browsers Affected
All
The text was updated successfully, but these errors were encountered:
Description
The
iron-localstorage
element handles the 'storage' event, which is fired when localStorage has been manipulated from another window. When localStorage.clear is called from another window, it clears all entries in the local storage and the 'storage' event is fired.iron-localstorage
should be firing the iron-localstorage-load-empty event, but does not.Expected outcome
'iron-localstorage-load-empty' should be fired when localStorage.clear is called from another window.
Actual outcome
'iron-localstorage-load-empty' isn't fired.
Live Demo
Steps to reproduce
iron-localstorage
element with a default value in the page.iron-localstorage
is listening for.Browsers Affected
All
The text was updated successfully, but these errors were encountered: