search

jpbedoya / google-axs-chrome

Automatically exported from code.google.com/p/google-axs-chrome
1 stars 0 forks source link

High Contrast causes html elements to render repeatedly in wrong positions #97

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Enable high contrast extension
2. Visit http://docs.scala-lang.org/overviews/core/futures.html
3. Scroll down, then when scrolling back up, the fixed position header renders 
repeatedly, "painting" the screen black and obscuring the page contents. (Can 
clear some of it by highlighting the text behind it.)

What is the expected output? What do you see instead?
Most noticably, fixed headers don't stay in place, then "paint" or "smear" the 
screen when scrolling up. Have seen similar repeated rendering with absolutely 
positioned elements, like voting controls on Quora or something (can't 
reproduce right now).

What version of the product are you using? On what operating system?
High Contrast 0.5
Chrome Version 26.0.1410.63
Mac OS X 10.7.5

Please provide any additional information below.
Started happening a couple weeks ago or so.

Original issue reported on code.google.com by kevinky...@gmail.com on 10 Apr 2013 at 4:10

Attachments:

GoogleCodeExporter commented 8 years ago 
I apologize. This behavior stopped at first when I turned off High Contrast, 
but now it's still happening. High Contrast is probably not to blame.

Original comment by kevinky...@gmail.com on 10 Apr 2013 at 4:18

GoogleCodeExporter commented 8 years ago 
This happens for me too. I do have High Contrast enabled. WinXP_SP3, Chrome 
v26.0.1410.64 m, High Contrast v0.5

Original comment by DavidH...@gmail.com on 3 May 2013 at 12:20

GoogleCodeExporter commented 8 years ago 
I found a fix. Go to chrome://flags, and find the two options involving
fixed position elements (use find "fixed"). Unfortunately, I have a
different computer now so I can't check exactly what settings fixed it for
me, but I know I disabled one or both of said options. (Note that you have
to restart Chrome to see the changes take effect.)

Seems unrelated to High Contrast -- probably started happening after some
Chrome update. I can't really imagine how an extension could affect Chrome
even when disabled, but someone with more familiarity should use their
discretion to close this issue if they don't think it's related to High
Contrast.

Original comment by kevinky...@gmail.com on 4 May 2013 at 9:10