Closed Bug 410689 Opened 17 years ago Closed 17 years ago

Cannot change text color on Google documents

Categories

(Core :: Widget: Cocoa, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 404433

People

(Reporter: hwaara, Assigned: jaas)

References

()

Details

(Keywords: regression, Whiteboard: [needs testcase])

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b3pre) Gecko/2008010304 Minefield/3.0b3pre

Steps to reproduce:

1. Create a new document
2. Write some text
3. Select the text, and try to change the color of it.

Expected result:

Color should be changed accordingly

Actual result:

No color change. Nothing happens.

Disclaimer:

I do not have time now to verify that the bug is in Gecko. There is a chance that it's Google doing something fishy; I'm reporting to be sure 1.9 does not ship, breaking some feature unknowingly.
No problem with the latest trunk on Windows XP.
WFM, Firefox 2008010304 on Linux.
Confirming bug, Firefox 2008010304 on MacOSX.

I noticed there is a difference in how the selection is highlighted -
on Linux the selection is greyed out when clicking on the "color menu",
after clicking on a color [and the menu closes] it becomes blue
(primary selection) again.  On MacOSX, the selection stays grey after
choosing a color.  In Firefox 2.0.0.11 on MacOSX it becomes blue again.

The regression window is: 2006-09-28-08 -- 2006-09-29-06
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2006-09-28+07%3A00&maxdate=2006-09-29+07%3A00&cvsroot=%2Fcvsroot
I'm guessing bug 326469.
Assignee: nobody → joshmoz
Blocks: cocoa
Component: Layout → Widget: Cocoa
Keywords: regression
QA Contact: layout → cocoa
Whiteboard: [needs testcase]
So apparently it's broken from the cocoa widgets switch.

Now that this is now confirmed, I suggest this should block 1.9 since Google documents is a pretty high-profile app.
Flags: blocking1.9?
Isn't this bug 404433 (which was FIXED while the last patch on bug 403232 was checked in, but should be broken again since that was backed out)?
You're right, Smokey.

And this bug is also fixed by my patch(es) for bug 403232.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Flags: blocking1.9?
You need to log in before you can comment on or make changes to this bug.