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
window.localStorage is not available in packaged apps. Use chrome.storage.local instead.
The chrome.storage.local interface is not available to Chrome Browser, only Chrome Apps. They key difference between the two is that window.localStorage is synchronous, but chrome.storage is asynchronous.
The simple "solution" is to simply prevent accessing window.localStorage when we are running as a Chrome App (detected by existence of chrome.storage?). This would mean that the supports test are run every time the Chrome App is started.
The proper solution would be to convert all of the supports test infrastructure to run asynchronously (because we could then support async tests). I'm not sure how that would integrate with synchronous APIs like ally.query.focusable(), though.
The text was updated successfully, but these errors were encountered:
Our supports cache saves its state in the
localStorage
. However @ryan-ludwig observed that Chrome Apps throw the following error when trying to accesswindow.localStorage
:The
chrome.storage.local
interface is not available to Chrome Browser, only Chrome Apps. They key difference between the two is thatwindow.localStorage
is synchronous, butchrome.storage
is asynchronous.The simple "solution" is to simply prevent accessing
window.localStorage
when we are running as a Chrome App (detected by existence ofchrome.storage
?). This would mean that the supports test are run every time the Chrome App is started.The proper solution would be to convert all of the supports test infrastructure to run asynchronously (because we could then support async tests). I'm not sure how that would integrate with synchronous APIs like
ally.query.focusable()
, though.The text was updated successfully, but these errors were encountered: