While using Orbit, I encountered an issue with the "supportsIndexedDB" function, which seems to be malfunctioning.
Upon testing in Chrome's incognito mode, the function correctly returns true, indicating support for indexedDB. However, when testing Firefox's private browsing mode, the function also returns true, which is incorrect. In reality, Firefox's private browsing mode does not allow the use of indexedDB, resulting in error messages such as error opening indexedDB *db-name* and DOMException: A mutation operation was attempted on a database that did not allow mutations.
To clarify, Firefox explicitly prohibits mutations to indexedDB while in private browsing mode. As a result, the "supportsIndexedDB" function should accurately reflect this behavior, returning false in such scenarios.
In my opinion, a more effective approach to handle checks for indexedDB support would involve something similar to this code:
While using Orbit, I encountered an issue with the "supportsIndexedDB" function, which seems to be malfunctioning.
Upon testing in Chrome's incognito mode, the function correctly returns true, indicating support for indexedDB. However, when testing Firefox's private browsing mode, the function also returns true, which is incorrect. In reality, Firefox's private browsing mode does not allow the use of indexedDB, resulting in error messages such as
error opening indexedDB *db-name*
andDOMException: A mutation operation was attempted on a database that did not allow mutations.
To clarify, Firefox explicitly prohibits mutations to indexedDB while in private browsing mode. As a result, the "supportsIndexedDB" function should accurately reflect this behavior, returning false in such scenarios.
In my opinion, a more effective approach to handle checks for indexedDB support would involve something similar to this code: