-
Notifications
You must be signed in to change notification settings - Fork 85
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
Firefox version is broken #28
Comments
Hey @nikocraft What version of Firefox are you using and what are the specs of your computer? My config: |
My config is 68.0 on windows 10, same page works in Chrome without any strange behaviour. See this video I just made for you on FF 68.0 https://www.youtube.com/watch?v=-jzH5_hfV-g I had to press enter two times on line 1 to be able to go to line 2 I'm not using any plugins on FF, it's a clean install. None of the behaviour seen in the video above happens in Chrome. All tested here: https://codesandbox.io/s/61yrlnlnmn |
I reproduce easily in codesandbox indeed. I will have a quick look. |
@elevatebart agree. In codesandbox it behaves strange but as you mentioned seems ok. |
I had exact same behaviour in my CMS. I had to turn off the plugin completly in the CMS. Anyways why would sandbox work just fine in Chrome but not in FF, something is strange with FF version. I've had people complain to me that it was giving them problems in FF with my CMS, that's why I started to investigate it and since we could not fix it I turned it off in FF, but also reported it here for you in hopes you'll be able to figure it out. |
Have your users complained about non-empty editors? Firefox is my main browser, I want to make sure it works for me ;-) |
What is non-empty editor? In my CMs initially there is no code in prism-editor, users have to put it there first if they want to customize stuff. So do you guys think it's a problem if editor is initiated empty and FF starts to missbehave because of this? |
Released new version v1 🎉 |
Hi are you aware that this component barly functions in Firefox, and it's exibiting strange behaviour. I'm using it for my CMS: https://www.youtube.com/watch?v=O-fO41eOp6o
Is there a chance you could take a look at this and see what's going crazy in FF? You can test it right in your demo links since the issue is there right when you start using it in FF.
The text was updated successfully, but these errors were encountered: