Text tool defaults to white

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Use text tool to type
2.
3.

What is the expected output? What do you see instead?
Should be black text, but instead it is white

Please use labels and text to provide additional information.
Problem started in r1812

Original issue reported on code.google.com by adrianbj...@gmail.com on 29 Jan 2011 at 12:54

[GoogleCodeExporter]

Hm, not for me, it's just black. Tried in FF, Chrome and Opera (all on Mac). 
Remind of your setup in which you see this?

Original comment by adeve...@gmail.com on 31 Jan 2011 at 4:09

[GoogleCodeExporter]

Ah, sorry for the incomplete report. It looks like it is just FF4. Still, it 
did work fine in FF4 in r1811, so maybe something can be tweaked, or a bug 
report filed with Mozilla. 

Original comment by adrianbj...@gmail.com on 31 Jan 2011 at 4:17

[GoogleCodeExporter]

Thanks, fixed in r1960.

Original comment by adeve...@gmail.com on 31 Jan 2011 at 8:03

• Changed state: Fixed

[GoogleCodeExporter]

Sorry to be a pain, but the text is changing to white again after resizing 
text. Another weird thing is that after it has gone white, you can't select 
black first, you must select another color which works and then black will work.

Original comment by adrianbj...@gmail.com on 31 Jan 2011 at 8:20

[GoogleCodeExporter]

Ah, sorry for not testing more. Try again with r1961.

The actual fill value is not changing by the way, it seems to be just a weird 
rendering bug as result of the text element being replace by its original, 
which is a workaround for issue 136 and issue 137 (also Firefox text bugs). 

Original comment by adeve...@gmail.com on 31 Jan 2011 at 8:29

[GoogleCodeExporter]

Sorry - still no better for me - maybe windows vs mac version of FF4?

Oh yeah, sorry about that - that would explain why trying to change to black 
doesn't do anything since it already is :)

Original comment by adrianbj...@gmail.com on 31 Jan 2011 at 8:47

[GoogleCodeExporter]

Maybe so... Ugh, back to the drawing board then. :(

Original comment by adeve...@gmail.com on 31 Jan 2011 at 8:52

• Changed state: Started
• Added labels: Browser-Firefox

[GoogleCodeExporter]

Not sure if it helps or not, but after changing size and "losing" the text, 
clicking on pretty much any button will bring the text back, so I wonder if 
that might hint at a workaround.

Original comment by adrianbj...@gmail.com on 31 Jan 2011 at 8:57

[GoogleCodeExporter]

Tried FF4b10 on WinXP, still doesn't turn white. Are you on Vista/7 perhaps? 
And you're sure you're testing the trunk? :)

My test includes:
- Creating text and typing
- Horizontally stretching text, then re-editing
- Vertically stretching text, then re-editing
- Rotating text, then re-editing.

Original comment by adeve...@gmail.com on 1 Feb 2011 at 2:53

[GoogleCodeExporter]

Ah - sorry I need to start being more specific before I drive you crazy. I am 
on XP, FF4b10, latest trunk. The problem happens when clicking the change font 
size up and down buttons on the top toolbar. I also see no problems when 
stretching, rotating etc.

Original comment by adrianbj...@gmail.com on 1 Feb 2011 at 3:10

[GoogleCodeExporter]

Heh, okay, see that too now. Thanks.

Original comment by adeve...@gmail.com on 1 Feb 2011 at 3:13

[GoogleCodeExporter]

Okay, try again for r1963.

Original comment by adeve...@gmail.com on 1 Feb 2011 at 3:24

[GoogleCodeExporter]

Beautiful :)

Original comment by adrianbj...@gmail.com on 1 Feb 2011 at 3:32

• Changed state: Fixed

[GoogleCodeExporter]

Thanks, though the same can't be said for the code:

'If is Gecko and element is text and is rotated and new value doesn't start 
with "url" and property is font-size, font-family, x or y and has text content, 
THEN make a copy of this element, delete the original and add it to selection.'

:(

Original comment by adeve...@gmail.com on 1 Feb 2011 at 3:40

[GoogleCodeExporter]

Yeah, I did have a little chuckle at that before - oh well it works :)

Original comment by adrianbj...@gmail.com on 1 Feb 2011 at 3:44

[GoogleCodeExporter]

Damn it, comment #14 won't fit into a tweet :-/

Buzz it is then!

Original comment by codedr...@gmail.com on 1 Feb 2011 at 4:06