-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
readOnly doesn't always work on chromiums web browsers #464
Comments
Thanks for reporting, I can indeed reproduce your issue on Chrome: https://stackblitz.com/edit/vitejs-vite-6qxz6c?file=main.js&terminal=dev I do not yet have an idea what could cause this issue, will look into it. Help debugging this would be welcome. |
Ok I have some clue:
Conclusion: one or multiple of the latest versions of the dependencies, after the versions uses in Workaround: define exact versions of the dependencies as of v0.23.7 in your own project. Next steps: figure out which dependency and which version of it introduces the issue. Then figure out if it is a bug in the dependency or in usage of it, and if needed report a bug at the affected dependency. |
We tried to isolate the dependency that could cause the issue and we narrowed it down to Well, thanks for the look! |
Ah, that helps a lot, thanks for debugging this! That explains it. In I'll try to make a small codemirror only demo to verify that and if so report the bug. |
I've reported the issue at the CodeMirror repo: codemirror/dev#1411 |
This issue has been fixed in |
It is indeed fixed! Thanks for the reactivity 😄 |
👍 |
Hi !
First of all, we are working in a tree shaking VueJs environnement with Vite 5.3.4 and we are trying to use the library to have a simple way to display (thus not edit) JSON data.
In my implementation and tests, I used Firefox and everything seemed perfect, but I did other tests on Brave and my n+1 did some on Chrome, and the readOnly didn't work there; we could still edit the JSONs in the views.
One of my coworkers did some tests as well, and if we use the standalone import of JSONEditor, the readOnly seems to be working as intended.
The text was updated successfully, but these errors were encountered: