Note that there are some explanatory texts on larger screens.

plurals
  1. POSolution for fixed & hidden div bug on Google Chrome
    primarykey
    data
    text
    <p>Problem: A div with <code>visibility:visible</code> inside a parent div with <code>position:fixed</code> and <code>visibility:hidden</code> causes rendering problems in Google Chrome. <a href="https://stackoverflow.com/questions/8568673/is-there-a-bug-in-chromes-css-visibility-rendering">Images and examples can be found here</a>.</p> <p>A week ago you could just add the <code>-webkit-transform:translateZ(0)</code> to the parent div and bug solved. But it isn't working anymore:</p> <ul> <li><a href="http://jsfiddle.net/bHzWN/show/" rel="nofollow noreferrer">Without <code>-webkit-transform</code></a></li> <li><a href="http://jsfiddle.net/kizu/bHzWN/6/show/" rel="nofollow noreferrer">With the hack</a>.</li> </ul> <p>Both are bugged.</p> <p>So, is there any solution? When you resize the window, it repaints the divs, also when you open the developer tools the bug disappears.</p> <p>So I've been trying to force a repaint with javascript (jQuery):</p> <pre><code>jQuery(window).scroll( function() { jQuery("#parentDiv").addClass("nothing"); jQuery("#parentDiv").removeClass("nothing"); }); </code></pre> <p>And it <strong>sometimes</strong> works (when a textfield is displayed inside the inner div). Really weird. Also tried hiding and displaying the div, adding css properties (fixed, bottom:0...) But nothing works fine.</p> <p>Any ideas?</p> <p>EDIT2: Seems like it only happens to me: 2 friends, using windows and the latest version (17.0.963.79) don't see the bug in the second link. But I still see it. I've reinstalled chrome under windows, and the bug is still there. I also have cleared the cache, but nothing changes. Am I the only one????</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload