"valid_elements" syntax for element removal when empty attributes needs example
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Half a day
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- documentation
Research direction
Start with the content-filtering documentation page at the linked valid_elements section and compare its current table with the syntax described in the issue. Document an example such as -span![!style] and clarify the control-character placement; consider the proposed grammar only if it fits the page. Done means the empty-element and required-attribute syntax can be understood without reading tinymce.js.
Written by the indexing model from the issue text.
Description
Documentation/Product Version
6.8.5
Links to Page(s) affected
https://www.tiny.cloud/docs/tinymce/latest/content-filtering/#valid_elements
Description of Issue
This entry:
"! - Enables removal of elements with no attributes such as . They can still have content though."
needs example, as I had to look into the code to find the "elementRuleRegExp" in tinymce.js and break it apart to figure out its' usage. Here, it needs to be something like "-span![!style]", the "!" in front of "[", whereas "!style" means a required attribute.
Suggested Fix
Adding the example with that comment would help.
Also, breaking this table up or adding a column to show what control characters can go where. Better than that, from that RegExp, having a template documented like BNF is far clearer (brief and incomplete, but you get the point):
=[","]
=["/"][]["[""]"]
= "+" | "-" | "#"
= "@" | "*" |
=
=
="" | "!"
- Dominant language
- JavaScript
- Stars
- 96
- Forks
- 219
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 26
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tinymce/tinymce-docs
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 38/100
tinymce/tinymce-docs#3436 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
tinymce/tinymce-docs#2778 · 2 comments ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
tinymce/tinymce-docs#2155 · 2 comments · 1 reaction ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
tinymce/tinymce-docs#1900 · 4 comments ·
All issues in tinymce/tinymce-docs
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
avniproject/avni-client#2135 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
babalae/bettergi-scripts-list#3674 ·
-
A-Release-Notes C-Editing D-Modest S-Ready-For-Implementation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bevyengine/bevy-website#2595 ·
-
ecosystem wording
Difficulty 1/5 Under an hour Newbie friendliness 90/100
matrix-org/matrix.org#3649 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
vadimdemedes/ink#1029 ·