magento / magento/community-features
Wysiwyg HTML tags to allow
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 46
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
TOPIC: what should wysiwyg allow?
I am increasingly getting warnings that wysiwyg is "temporarily" allowing certain tags, and this of course worries me that at some point these will get locked out.
One option is that this is made extensible/editable in an official, documented manner (that isn't overwritten by releases), the other option is to have a discussion and get these lists extended?
missing tags - these seem harmless why aren't they in?
blockquote / q for quotes
abbr / cite for references (semantic/machine readable/accessibility)
code / pre for unformatted
details / summary for a hide/show mechanism in the browser
dl dd dt
figcaption for figure (accessibility)
picture (for responsive)
del / s / ins for text removed/ added that needs to remain visible as such (legal requirements in some parts)
mark (for highlighter)
small, sub, sup
thead / caption for table (they improve accessibility!)
data - for structured data/search engine enhancements
col colgroup section article aside - document structure
svg - ok that's probably more complicated
should be allowed in every tag:
aria tags - some of us try to keep things accessible
making sense in static wysiwyg
role
aria-colcount
aria-colindex
aria-rowcount
aria-rowindex
aria-colspan
aria-rowspan
aria-details
aria-expanded
aria-flowto
aria-hidden
aria-label
aria-level
aria-roledescription
specific combinations
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
The issue names no files, tests, or entry points. First trace how WYSIWYG HTML and ARIA allowlists are configured and preserved across releases, then determine whether the request needs documented extensibility or a defined tag-list expansion. Done means the scope is agreed and the resulting behavior is covered by implementation and documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100