StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POIs there a bug in Chrome's CSS visibility rendering?
primarykey
Id
8568673
data
AcceptedAnswerId
0
AnswerCount
2
ClosedDate
CommentCount
15
CommunityOwnedDate
CreationDate
2011-12-19T22:54:55.900
FavoriteCount
2
LastActivityDate
2012-03-11T18:21:03.670
LastEditDate
2012-01-16T02:49:03.293
LastEditorUserId
407254
OwnerUserId
407254
ParentId
0
PostTypeId
1
Score
12
ViewCount
6037
LastEditorDisplayName
text
Body
<p>There seems to be odd behavior in Chrome 15+ when using this particular combination of CSS properties, namely an outer element with visibility hidden and fixed positioning and an absolutely or relatively positioned inner element that has an override on visibility.</p> <pre><code><html> <head> <title></title> </head> <body> <div style="position:fixed;visibility:hidden;"> <div style="position:absolute;visibility:visible;"> <img src="https://www.google.com/intl/en_com/images/srpr/logo3w.png" /> </div> </div> <script type="text/javascript"> for(var i=0; i<100; i++) { document.write("<br />"); } </script> </body> </html> </code></pre> <p>The code snippet above produces this image when scrolled. <img src="https://i.stack.imgur.com/KSmfh.png" alt="Chrome visibility issue"></p> <p>The fact that both relative and absolute positioning both reproduce the behavior can be chalked up to the fact that for this particular DOM absolute positioning is equivalent to relative positioning.</p> <p>In the case that this markup is valid and does have defined behavior, this points to a bug in the browser/rendering engine, and it looks like a performance optimization gone bad, especially given that this behavior was introduced with the Chrome 15 update.</p> <p><a href="http://jsfiddle.net/bHzWN/show/" rel="noreferrer">JSFiddle link</a> courtesy of Sparky672</p> <p>Update:</p> <p>This behavior has been reported to the <a href="https://bugs.webkit.org/show_bug.cgi?id=76126" rel="noreferrer">WebKit Bugzilla</a> and seems that the changeset that introduced the bug has been identified. </p>
Tags
<css><google-chrome>
Title
Is there a bug in Chrome's CSS visibility rendering?
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USNovikov
UserOwnerUserId
1. USNovikov
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
  singulars
  LinkTypeLinkTypeId
  LTLinked
2. PL
  singulars
  LinkTypeLinkTypeId
  LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
2. PO
  singulars
  PostTypePostTypeId
  PTAnswer
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  POIs there a bug in Chrome's CSS visibility rendering?
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
2. VO
  singulars
  PostPostId
  POIs there a bug in Chrome's CSS visibility rendering?
  UserUserId
  USNovikov
  VoteTypeVoteTypeId
  VTBountyStart
3. VO
  singulars
  PostPostId
  POIs there a bug in Chrome's CSS visibility rendering?
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.