What is the expected result?
Page should be static, and Chrome should behave.
What happens instead?
Page rapidly flickers, and Chrome uses 100% CPU.
break down:
1. The page renders without scroll bar, and it is long enough to warrant a
scroll bar
2. Adds a scroll bar, which rearranges the page making it narrower but due
to the layout of the page, also shorter and causes it to not need a scroll
bar.
3. see step 1
This also happens in Safari at this specific size.
Attachments:
ChromeBug.tiff 304 KB
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
chro...@googlecode.com
unread,
Apr 27, 2013, 3:10:50 AM4/27/13
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
Correction to #8: updateScrollbars() is called recursively (depth=1) when
the content size is 978x594 and 993x591.
The page contains the following CSS rule:
@media screen and (min-width:982px) {
...
}
The rule for wider screen produces higher layout (993x594) than the default
rules does (978x591).
There are also some transition animations on some elements. The sizes
978x594 and 993x591 are temporary sizes after the vertical scrollbar is
created/removed at the beginning of the transition animation. The
combination of the abnormal @media rule and the transition animation causes
the flickering.
This looks a fundamental problem of non-overlay scrollbars. I'd mark this
issue WontFix, or suggest outreach to wikipedia.
Attached the reduced test case.
Attachments:
testflicker.html 588 bytes
chro...@googlecode.com
unread,
May 6, 2013, 5:22:18 PM5/6/13
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
If we could detect this case the right thing to do would be to add a
disabled vertical scrollbar to the page. Detecting it in the case of
@media + transitions might be hard.
If we wanted to treat this as an evangalism bug, what would our
recommendation to wikipedia be?
chro...@googlecode.com
unread,
May 6, 2013, 6:20:23 PM5/6/13
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
The spec seems wrong - MQs need to be based on the device's capabilities,
disregarding any content or styles. Otherwise, you run into trivial
circular dependencies.
Allowing scrollbars to influence the 'width' MQ violates both of these - it
depends on the page's content *and* styles. That's super-bad.
We should switch to ignoring scrollbars all the time, and give feedback to
the CSSWG that this needs to be changed.
chro...@googlecode.com
unread,
May 6, 2013, 6:38:24 PM5/6/13
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
I believe the CSS spec is saying the same thing. By "including the size of
a rendered scrollbar", it means to use the total width of the viewport,
e.g. not subtracting the space used by scrollbars.
chro...@googlecode.com
unread,
May 6, 2013, 6:48:24 PM5/6/13
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message