Closed Bug 7992 Opened 26 years ago Closed 25 years ago

[TABLE]Implement SetBackgroundColor when in Table or Cells

Categories

(Core :: DOM: Editor, defect, P3)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: Brade, Assigned: cmanske)

References

Details

Based on conversation in the editor newsgroup, move SetBackgroundColor to be in a more correct class (nsTextEditor?).
Status: NEW → ASSIGNED
Summary: SetBackgroundColor in nsHTMLEditor → Implement SetBackgroundColor in both nsHTMLEditor and nsTextEditor
Target Milestone: M8
The version in nsTextEditor should just set the document background color. The version in nsHTMLEditor should set the table or cell background for the appropriately-selected element or the cell background if text selection is inside a single cell.
Target Milestone: M8 → M9
I'll implement setting the table or cell background when I get into table work in M9, so I'll take of this then.
Target Milestone: M9 → M11
Changed to M11
Target Milestone: M11 → M12
Changing target
*** Bug 10655 has been marked as a duplicate of this bug. ***
Summary: Implement SetBackgroundColor in both nsHTMLEditor and nsTextEditor → Implement SetBackgroundColor when in Table or Cells
Changing summary to better describe the task. nsTextEditor doesn't exist anymore, so the task is to detect when selection is in a table or cell and set background on that instead of the entire page.
Summary: Implement SetBackgroundColor when in Table or Cells → [TABLE]Implement SetBackgroundColor when in Table or Cells
Target Milestone: M12 → M14
pushing table tweaking out to M14
Target Milestone: M14 → M15
moving to m15 - load balance
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Depends on: 24410
Resolution: --- → FIXED
Target Milestone: M15 → M14
This is fixed, but depends on 24410 to verify. You can try to set the color of a cell, but it will look like only the cell border is colored. Karnaze will fix 24410 for M14.
I'll need help verifying this one please..thanks!
Status: RESOLVED → VERIFIED
verified in 1/19 build.
You need to log in before you can comment on or make changes to this bug.