Home › Forums › Bug Reports › Visual Editor issue with Firefox
Hi,
When editing in Firefox, the visual (WYSIWYG) editor custom field appears to be disabled. There’s no way to enter text. Clicking in the field has no effect.
There’s no problem in Chrome or even Edge.
Might not be an ACF bug, though, I don’t know.
Patrick
Hi again,
I should have mentioned that the problem occurs even on a clean WP 5.6 installation using the default theme and with no other plugins installed beside CPT UI and ACF.
Well, clearing the Firefox cache has fixed the problem. Don’t ask me why.
Sorry.
Hi,
Actually, clearing the Firefox cache was just a temporary fix. The problem is back today even for WYSIWYG custom fields that worked correctly after the cache clearing I made yesterday.
I have the same problem:
WP 5.6 (clean install or with plugins – doesn’t matter)
ACF PRO 5.9.4
FF 85.0 (64 bit) on OSX 10.14.6
Flushing cache doesn’t work in my case.
My guess is that there us a JavaScript error that is preventing the editor from initializing. Are you seeing any errors in console?
Hi,
Not 100% sure but it seems that the problem didn’t occur again since I have installed Advanced Editor Tools (previously TinyMCE Advanced).
I’ll have a look at the console whenever the problem re-appears.
Patrick
Hello,
this is console output in page edit with wysiwyg editor custom fields:
This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. post.php
JQMIGRATE: Migrate is installed, version 3.3.2 load-scripts.php:5:709
MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead. 2 wp-tinymce.js:3:8856
Nothing else appears there even during custom fields editing.
I have the same issue. Did anyone workout how this was resolved?
Thanks,
D
Apologies for resurrecting an old thread, but I am still seeing this error on:
– WordPress 6.7
– ACF Pro 6.3.11
– Firefox 132.0.2 (both Windows 10 and macOS)
I am testing on a fresh install of WordPress using the stock Twenty Twenty-five theme with only ACF Pro enabled. I created a single field group with a single WYSIWYG field.
When opening the editor, the field appears to load normally, but after refreshing the field does not show any content and becomes unresponsive to any input in the main editor area, although I am able to click on the buttons in the TinyMCE toolbar as well as the Visual/Test toggle.
There are no errors in the Firefox console, only the following which appear to be warnings:
Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content. markup.js:250:53
This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. post.php
JQMIGRATE: Migrate is installed, version 3.4.1 load-scripts.php:5:981
downloadable font: Glyph bbox was incorrect (glyph ids 11 19 20 21 55 58 79 96 101 115 116 120) (font-family: "tinymce" style:normal weight:400 stretch:100 src index:1) source: http://acf-wysiwyg-issue-test.local/wp-includes/js/tinymce/skins/lightgray/fonts/tinymce.woff
Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content. ce917c4a-18c0-4680-a2b9-2d1ec833f72d
MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead. block-editor.min.js:21:494336
MouseEvent.mozInputSource is deprecated. Use PointerEvent.pointerType instead. block-editor.min.js:21:494336
MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead. tinymce.min.js:2:8857
MouseEvent.mozInputSource is deprecated. Use PointerEvent.pointerType instead. tinymce.min.js:2:8857
After some more testing, it appears that the issue is not present when using WordPress 6.6.2
I also have this problem. Working on a lot of websites with ACF Pro and similar plugin/theme configuration and do not have the problem on other pages with lower WP version.
Seems to be a new bug with WP 6.7.X … Will this be solved?
In Chrome everything works…
You must be logged in to reply to this topic.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Privacy Policy. If you continue to use this site, you consent to our use of cookies.