User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20120822 Firefox/16.0 Build ID: 20120822042007 Steps to reproduce: New profile install statusbarex and enable the addonsbar navigate to http://www.chia-anime.com/alpha/K (url can be substituted with any long page, a facebook wall or photo comment block for instance) zoom in a few levels (ctrl-+ 3x) then refresh Actual results: scrollbar will no longer update Expected results: scrollbar continues to work
MC Working 20120727030508 http://hg.mozilla.org/mozilla-central/rev/8b96a33ecbd2 Broken 20120728030524 http://hg.mozilla.org/mozilla-central/rev/2abd21593e57 Tinderbox-MC Good 20120726215017 http://hg.mozilla.org/mozilla-central/rev/8b96a33ecbd2 Bad 20120727015618 http://hg.mozilla.org/mozilla-central/rev/399aff2fb74f Tinderbox-MI Good 20120726180140 http://hg.mozilla.org/integration/mozilla-inbound/rev/4bfa8a24fe41 Bad 20120726210130 http://hg.mozilla.org/integration/mozilla-inbound/rev/5fe4c57fb73e
Component: Untriaged → Layout
Product: Firefox → Core
Nothing in https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=4bfa8a24fe41&tochange=5fe4c57fb73e jumps out as the obvious culprit.
I'm aware I'm re-narrowing the range, when i first tried there were less builds in the Mozilla Inbound folder then there are now. For example, there is a build for 20120726200916 now in the folder between those 2 tinderbox builds.
Hmm, i might have been in the PGO inbound folder before or something, because 20120726174818 exists with 4bfa8a24fe41 but 20120726180140 does not with 4bfa8a24fe41 alright, MI Good 20120726195817 http://hg.mozilla.org/integration/mozilla-inbound/rev/541286c00397 Bad 20120726200916 http://hg.mozilla.org/integration/mozilla-inbound/rev/73d5c4461f12
unless these are mobile only, my suspects are bug 777617 or bug 777924 20120726195817 http://ftp.mozilla.org/pub/mozilla.org/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-win32/1343357897/ 20120726200916 http://ftp.mozilla.org/pub/mozilla.org/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-win32/1343358556/
(In reply to Danial Horton from comment #4) > MI > Good > 20120726195817 > http://hg.mozilla.org/integration/mozilla-inbound/rev/541286c00397 > > Bad > 20120726200916 > http://hg.mozilla.org/integration/mozilla-inbound/rev/73d5c4461f12 In other words: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=541286c00397&tochange=73d5c4461f12
and this has now followed 17 to aurora -_-
Hardware: x86_64 → x86
Version: 16 Branch → 17 Branch
I can confirm this, as I'm receiving bug reports on my add-on (NoSquint) after users are upgrading to Firefox 17. I've created a screencast showing the issue and how to reproduce it. It is highly sporadic. http://youtu.be/yS6ZPymowdo
I should have mentioned: I can reproduce this issue with a clean profile. No add-ons are needed, although with NoSquint the problem is much more consistent (probably because NoSquint modifies the zoom level at a slightly different time during page load than native Firefox does).
A NoSquint user filed a bug at https://github.com/jtackaberry/nosquint/issues/50 which may have more relevant details. I can reproduce this on Ubuntu 12.10 x86_64, and original submitter of the NoSquint bug was using Ubuntu 11.10 x86. I've received other bug reports by email and have asked them further information about their platform, but considering I'm seeing on different architectures on Linux and Danial saw it on Windows x86, this looks like a platform agnostic bug.
Status: UNCONFIRMED → NEW
status-firefox17: --- → affected
tracking-firefox18: --- → ?
tracking-firefox19: --- → ?
tracking-firefox20: --- → ?
Ever confirmed: true
I think this is fixed in nightlies. So it would be good to find out what fixed this so we can make sure to uplift it to the right places.
Not able to reproduce this with 18b1.
status-firefox17: affected → ---
tracking-firefox18: ? → ---
tracking-firefox19: ? → ---
tracking-firefox20: ? → ---
(In reply to Timothy Nikkel (:tnikkel) from comment #11) > I think this is fixed in nightlies. So it would be good to find out what > fixed this so we can make sure to uplift it to the right places. Danial, do you agree this is fixed?
This has been fixed for a very very long time.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.