home-assistant / frontend

:lollipop: Frontend for Home Assistant
https://demo.home-assistant.io
Other
4.05k stars 2.77k forks source link

Icon store exception in Firefox private mode #16175

Closed steverep closed 9 months ago

steverep commented 1 year ago

Checklist

Describe the issue you are experiencing

Uncaught (in promise) DOMException: A mutation operation was attempted on a database that did not allow mutations. iconsets.ts:84:2 81312 iconsets.ts:84 AsyncFunctionThrow self-hosted:814 (Async: async) 81312 ha-icon.ts:37 Webpack 17

Describe the behavior you expected

No exception

Steps to reproduce the issue

Open login page in Firefox private mode and check the console

What version of Home Assistant Core has the issue?

2023.4.x

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Firefox 111 (private mode)

Which operating system are you using to run this browser?

Windows 10

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

See above

Additional information

No response

github-actions[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

steverep commented 1 year ago

Still an issue

github-actions[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 9 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

steverep commented 9 months ago

Can't reproduce anymore