-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
CSS Class Auto Suggestion #15077
Comments
Cheers @Soean. I'll check the other open issues to see whether they discuss auto suggestions for previously used class names. Edit. Those open issues are closer to where I anticipated my feature suggestion eventually leading; my intention was to open the conversation. I hadn't realised we were this far along -- I had a brief look before posting, though (wading through so many issues/requests/suggestions is not easy. Maybe we need an A1, A2 and Adopted tag for considered suggestions? 'A#' because A comes before B...). I can see those open issues working well as a CPT. I'll read through them and post there if appropriate. Again, thank you. |
@Soean not everyone can use Block Styles, cause it requires PHP knowledge to create own block styles. Thats why we have the option for Additional CSS Classes, as CSS is more accessible for non Developers and Designers. I really support the suggestion for showing extisting Custom CSS classes, as it would make it really easier to use custom classes! |
See also: #19367 |
I know this is old issue, but you can try using this plugin: https://wordpress.org/plugins/block-class-autocomplete/ It utilizes the PHP block-class-autocomplete.mp4There is an issue though in latest WP that completely changed the way the core input component was added, so now it is showing the default field and this custom field. They do sync, but I'm currently trying to figure out if that can be corrected. |
I think it would be useful for CSS classes added in a block's Advanced tab to be stored in the database and suggested for reuse whenever the Advanced tab is opened similar to the way categories are suggested. This would prevent authors entering wrong class names and would stop authors forgetting about classes that are available to use already.
Would this be easy to implement?
The text was updated successfully, but these errors were encountered: