Open GoogleCodeExporter opened 8 years ago
This happens in general, on sites with complicated DOM structures. Due to bugs
in the webkit renderer which chrome uses various calculations have to made in
order to figure out what text you're hovering over. On a complicated site this
sometimes leads to text detection even on blank areas.
I can probably figure out someday how to get everything to work, or maybe
webkit will be patched but until then go to options and turn off highlighting
which will prevent your cursor from leaving the comment fields.
Original comment by melin...@gmail.com
on 29 Feb 2012 at 5:33
Original issue reported on code.google.com by
AhmedHan
on 27 Feb 2012 at 7:04Attachments: