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
TinyMCE with HTML5 Required attribute set won't allow save - no on-page error message #1893
Comments
TinyMCE adds style="display:none" to the
|
@BrendonKoz Thanks, I didn't realize the HTML5 option was there. It's not supposed to be there because of course TinyMCE is not an HTML5 input type. I have pushed an update that removes that configuration setting. @matjazpotocnik I'm not sure I understand what that does? Does the focus event transfer to the TinyMCE input somehow? |
@matjazpotocnik Thanks, that's a creative solution, I like it! :) Though I'm not confident that it would survive across browsers and also wonder if the user starts typing, would it then go directly into the 1px wide textarea, bypassing TinyMCE. So I'm thinking we should probably just stick with disabling the HTML5 required option for TinyMCE, to play it safe. |
@ryancramerdesign I still get errors about an unfocusable element. I had to delete |
Short description of the issue
When applying both "required" attributes to a TinyMCE field (
Required?
, andAlso use HTML5 "required" attribute?
), any pages created (only tested on new page) using a template with this configuration on that field will fail to save. Removing the HTML5 required attribute and relying on ProcessWire's processing of the form to verify the required field has been filled in appropriately.Expected behavior
The expected behavior is that PW will identify that the richtext editor field has proper content/value and the page can be saved.
Actual behavior
The page will not save. The browser developer Console fills the page with
is not focusable
error messages. The page auto-scrolls to the first (if there are multiple) TinyMCE field on the template, but there are no visible error messages on the page. (Using Firefox v124.0b6), should it matter.)Optional: Screenshots/Links that demonstrate the issue
Optional: Suggestion for a possible fix
A temporary fix is to disable the
Also use HTML5 "required" attribute?
setting for any/all TinyMCE fields, if set.Possibly related to #799 (comment) ?
Steps to reproduce the issue
3 In the "Input" tab of the TinyMCE field, check/enable the
Required?
attribute, and once set, also set theAlso check/enable the HTML5 "required" attribute?
field of the TinyMCE field's settingsSetup/Environment
The text was updated successfully, but these errors were encountered: