Open Bug 1812675 Opened 2 years ago Updated 2 years ago

composer should support highlighting

Categories

(Thunderbird :: Message Compose Window, enhancement)

Thunderbird 102
enhancement

Tracking

(Not tracked)

People

(Reporter: hrdubwd, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:109.0) Gecko/20100101 Firefox/109.0

Steps to reproduce:

Tried to find a way of highlighting text (especially to draw attention to earlier content).

Actual results:

No such function visible.

Expected results:

Simply, a means could be provided for highlighting text (as in Acrobat or a word processor), preferably by a 'pen' tool selection, then drag, or by selecting text and clicking a 'highlight' button.
Yellow is the obvious colour to use as default, but the possibility exists for other pastels, as in typical sets of highlighter pens.
This can probably be done with html, I assume, but such code is probably not obvious to many users, as it is obscure to me, but if used it woudl be much more complicated to implement than the suggestions now.

Status: UNCONFIRMED → NEW
Component: Untriaged → Message Compose Window
Ever confirmed: true
Summary: highlight text → composer should support highlight (<mark>) element

Thanks, as I thought - it exists (although I was unaware of it exactly), but how does one use that in replies? It should be simple fast to implement. Having to edit in html is not for many ordinary users (like me) anyway?

Doesn't look like document.execCommand can handle <mark>. There is hiliteColor though, if one uses the css mode.

Summary: composer should support highlight (<mark>) element → composer should support highlighting

Is that supposed to be for the ordinary user?

No, just an implementation note.

As a follow-up, while just selected text can have the colour (and other attributes, of course) changed, this does not work for background colour - the whole page is changed. For consistency, just the selected region should be changeable. This might be the best solution to the request.

You need to log in before you can comment on or make changes to this bug.