I want to use the HTML code <mark> in the newsletter and still be able to edit the draft page in VisualEditor. Right now, adding <mark> produces nowiki tags, and opening a page with <mark> already on it prevents editing the marked text (alienated content).
Version: unspecified
Severity: enhancement
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | Jdforrester-WMF | T49780 VisualEditor: Tools to set/unset text with annotations (tracker) | |||
| Open | Feature | None | T66376 VisualEditor: Tool to set/unset text as highlighted (<mark>) |
Change 141605 had a related patch set uploaded by Jforrester:
Split out ve.{dm,ce}.TextStyleAnnotation into parts, add other annotations
Change 141605 merged by jenkins-bot:
Split out ve.{dm,ce}.TextStyleAnnotation into parts, add other annotations
(In reply to Elitre from comment #3)
Will this only allow marking the text in yellow?
It will mark the text with <mark>. It's up to users' browsers to decide how to show it as marked, but yes, all major browsers ape the neon-lemon-yellow highlighter colour to show this currently.
(In reply to Elitre from comment #5)
I'm unhappy. I demand the ability to pick my favorite color when
highlighting.
Talk to W3C. ;-)
No! Google Docs allows highlighting text in the color I want. Please make that happen somehow?
(In reply to Elitre from comment #7)
No! Google Docs allows highlighting text in the color I want. Please make
that happen somehow?
That's not highlighting with <mark>, that's setting text background colour which is bug 73041.
I had seen that, but given that it didn't mention the word "text" and that elsewhere you were so strongly against the idea, I had to assume it was actually about the page color.
The ability to set a text background in whatever color we want (#FC0FC0, in my case) will IMHO make using <mark> unnecessary.