Selecting some black text in Google Chrome makes that text white in Ubuntu 12.04

[Andrei]

This is present in Ubuntu 12.04. This was not present in 11.10.
Often, selecting black text from Google Chrome's extension, Google Talk, is making the selected text appear white, on the white background; hence not being readable. Sometimes it doesn't, the text remains black, and the selecting font is, of course as it should be, orange.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/944358/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Adolfo Jayme Barrientos (fitojb)]

Thanks for your bug report.

Can you upload a screenshot? And perhaps this is a bug in Chrome? This happens with other themes?

[Andrei (andrei-doom)]

Like it says in the screenshot, that empty white area is actually some black text that was selected. And like I said in the bug description, the selection makes the text appear white on the white background, hence not being readable.

[Adolfo Jayme Barrientos (fitojb)]

OK, I've seen that issue happening sometimes along with a different font rendering. Though I'm not able to reproduce it, seems to happen randomly in pages with web fonts. Not really a bug in light-themes, I'm marking this affecting chromium. If you know how to reproduce this consistenly, I reccomend you to file a bug upstream against Chromium at <http://crbug.com>

[Andrei (andrei-doom)]

I understand, but why isn't this bug present in 11.10 ? As soon as I've switched to 12.04, this happened.

[Gabe Gorelick (gabegorelick)]

The package you want is chromium-browser.

[Andrei (andrei-doom)]

Anytime now....

[Andrei (andrei-doom)]

Bump

[Andrei (andrei-doom)]

This appears to be fixed in 12.10 Alpha 1, kernel 3.4 and Chrome 19.0.1084.56. I'll come back if I find a regression.