97840 - HTML Editor/Composer: Implement text highlight feature to apply background color to selected text (inline css <span style="background-color:xxx">)

Status: RESOLVED DUPLICATE of bug 318600

(SeaMonkey :: Composer, defect)

Description

[TucsonTester1]

Build 20010830 Netscape6/6.1b1

1.  Open a blank composer document to edit.
2.  Type some random text.
3.  Using your mouse, highlight some of the text.
4.  In the Text Formatting bar, click the text color pallette and choose a text
color other than black or white.
5.  Leaving the text highlighted, click on the text background color pallette.

Result:
A pallette opens for Page Background color.  This functionality is located near
the bottom of the Format menu already, and I expected to find it there.  I
didn't expect to find it where a text background color pallette should be. 

I have seen this occur on OS 8.6, OS 9.1, and OS X only.  I have not tested
other platforms. 

Date:
8/31/01

Notes:
The only way I could figure out how to change the text background color is by
manually entering a span style="background-color: tag.

Comment 1

[Greg K.]

Reporter, please retest using a Mozilla (not Netscape) build.

Comment 2

[James Baxter]

Greg: This is a QA Build - should still be valid.

Comment 3

[Syd Logan]

spam composer change

Comment 4

[Kathleen :Brade]

We need to fix the color chips on the formatting toolbar.

Comment 5

[Jesse Ruderman]

See also bug 121210, can't select paragraph background color easily.

Comment 6

[Charles Manske]

The overlapping squares on the toolbar represent the standard 
'Forground / Background' type of widget used in graphic programs. If you click
on the square that is "behind", that brings up colorpicker for cell/table/page
background. As brade mentions, this UI will probably change to a new pattern
given the new "text background" icon added when in CSS attribute mode (set in 
composer prefs (see bug 121210).

Comment 7

[Kathleen :Brade]

we should discuss this at our next meeting (esp. if Daniel is around)

Comment 8

[Syd Logan]

I agree CSS composing brings this issue to the front, but I don't see it as
EDITORBASE by our definition (function works as intended, and I'd like to see
some usability people involved before we make any decisions).

Comment 9

[Kathleen :Brade]

*** Bug 121210 has been marked as a duplicate of this bug. ***

Comment 10

[Syd Logan]

only nsbeta1+ bugs can have milestones, resetting to ---

Comment 11

[Charles Manske]

We need 3 icons! Should be done for 1.0

Comment 12

[Daniel Glazman (:glazou) (not active in Mozilla any more)]

I have a proposal on my plate. Just need some find some other minutes to
dive into my favorite drawing tool.

Comment 13

[Kathleen :Brade]

-->glazman for his work (0.9.9?)  
When he has attached images he can reassign to cmanske or check in the work himself.

Comment 14

[Kevin McCluskey (gone)]

Marking nsbeta1-

Comment 15

[Kevin McCluskey (gone)]

Setting Milestone to Moz1.1

Comment 16

[Charles Manske]

Glazman's text highlighting is now working when you are in "CSS Mode" 
(set in Composer preferences), so this is now fixed.
Use the "highlight" toolbar button to bring up colorpicker for text background
We know we have issues with the toolbar widget design, but those are covered in
other bugs.

Comment 17

[Kathleen :Brade]

reopen bug since I don't think this has been addressed yet (toolbar
positioning/order/placement of color chips)

Comment 18

[Charles Manske]

Removing '-' for Buffy consideration and taking bug.

Comment 19

[Samir Gehani]

Composer triage team: nsbeta1-

Comment 20

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 21

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 22

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 23

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 24

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 25

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 26

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 27

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420

Comment 28

[Thomas D. (:thomas8)]

This problem isn't resolved while we've got too many bugs for the same issue in TB and SeaMonkey. This seems to be one of the oldest occurences and comes with reasonable STR which also point to the wrong design of the toolbar color picker.

-> reopening with intention of consolidating here

Comment 29

[Thomas D. (:thomas8)]

Oh, this bug was for the same problem in HTML Editor component aka "Composer" of SeaMonkey Suite.
I don't know enough how the internals are connected, so moving back to previous product and component.
Bug probably still around as seen from other bugs filed against SM and TB. New summary probably still applies and describes the problem better and more retrievable.

Comment 31

[Rainer Bielefeld]

Only 1 issue per Bug Report, I reduce this one to the inline css - RFE, and for that one we already have "Bug 318600 - Need text highlight feature to apply background color to selected text (inline css <span style="background-color:xxx">) / Page background color picker is misplaced"

For the bad UI we need a different report (may be already one does exist?).