- Issue created by @catch
- 🇫🇷France dqd London | N.Y.C | Paris | Hamburg | Berlin
+1 for raising this. My vote for it and 100% agree with the argumentation and reasons. And it would close a group of other issues. Additionally it minimizes the efforts to keep track with those tips and all possible combinations of allowed tags etc and it never really looked well seated under the textareas of body and comment fields and was kind of circumventing to style. And since we do not have any hard wired dependencies in core with this part of filter.module it would be mainly removing the respective parts in web/core/modules/filter (tips) and making sure that it does not break contrib in case that modules use tips to place their own (if any?)
When formatting tips are actually needed, we already provide field descriptions which site admins can edit - this would allow them to give a couple of markdown examples, link to external resources etc.
And which gives far more flexibility. Also in how it looks or how it is implemented (markup). Only drawback is that it do not change it's tips automatically regarding the allowed tags when switching between formats, I worry? Maybe we should provide a token which picks up the allowed tags from the formats to be used in the field description?
- 🇫🇮Finland lauriii Finland
+1 for the removal as discussed during the Burgas onsite. The content on this page isn't relevant in the world of CKEditor 5.
- First commit to issue fork.
- 🇬🇧United Kingdom catch
MR looks good so far, except I think we probably need to remove the method from FilterInterface rather than deprecate it.
We also need to remove the filter tips link from
Drupal\filter\Element
and should deprecate the route that it points to (which we can do now after https://www.drupal.org/node/3317784 → ).There are some templates in claro/stable etc. not sure if we can remove those yet or if it would need to happen in a 12.x-only issue.