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
For the most part components work with no issues, but certain components cause issues when used. In particular, I noticed Dialogs and Popper type components. After use, they cause the page to start throwing this error.
Error: Permission denied to access property "apply"
The issue is present in the latest release.
I have searched the issues of this repository and believe that this is not a duplicate.
Current Behavior 😯
The page works normally until a dialog or popper component is used.
Then it starts to interfere with normal scripts on the page, throwing things like:
Error: Permission denied to access property "apply"
Expected Behavior 🤔
Honestly, I'm okay if web extensions are not a supported use case for MUI. I'm more wondering if someone has insight into why these components cause issues. For now I'm rolling a custom modal / popup that doesn't cause issues.
Steps to Reproduce 🕹
Hard to include steps on this. Basically you need to have a web extension on a page, open a dialog in the extension, then use the page and see the error.
Context 🔦
Using MUI in a web extension.
Your Environment 🌎
Firefox
Tech
Version
Material-UI
v4.9.5
React
Experimental (concurrent mode)
Browser
Firefox 74
The text was updated successfully, but these errors were encountered:
Hard to include steps on this. Basically you need to have a web extension on a page, open a dialog in the extension, then use the page and see the error.
We need a complete repro for this. It's the first time I've heard about issues in web extensions so we don't have the bandwidth to debug these one-off use cases without some help from contributors.
I'll try and figure out a way to reproduce it without extensions. It may require installation of a web extension though. Would that be okay for a reproduction?
Basically I think I could make a code sandbox, but in addition one would have to install an extension.
@andrewkfiedler This sounds like a violation of a security constraint of Firefox. Let us know if you find the origin of the problem. Closing until then.
For the most part components work with no issues, but certain components cause issues when used. In particular, I noticed Dialogs and Popper type components. After use, they cause the page to start throwing this error.
Current Behavior 😯
The page works normally until a dialog or popper component is used.
Then it starts to interfere with normal scripts on the page, throwing things like:
Expected Behavior 🤔
Honestly, I'm okay if web extensions are not a supported use case for MUI. I'm more wondering if someone has insight into why these components cause issues. For now I'm rolling a custom modal / popup that doesn't cause issues.
Steps to Reproduce 🕹
Hard to include steps on this. Basically you need to have a web extension on a page, open a dialog in the extension, then use the page and see the error.
Context 🔦
Using MUI in a web extension.
Your Environment 🌎
Firefox
The text was updated successfully, but these errors were encountered: