Last modified: 2012-05-01 02:17:16 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T38308, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 36308 - Top bar not following during scrolling
Top bar not following during scrolling
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
PageCuration (Other open bugs)
unspecified
PC Windows 7
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-27 19:57 UTC by Oliver Keyes
Modified: 2012-05-01 02:17 UTC (History)
2 users (show)

See Also:
Web browser: Firefox
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
Screenshot (178.73 KB, image/png)
2012-04-27 19:57 UTC, Oliver Keyes
Details

Description Oliver Keyes 2012-04-27 19:57:19 UTC
Created attachment 10480 [details]
Screenshot

See the screenshot. It's a very, very precise bug; if I scroll after loading the page fresh, the top bar follows nicely. If I then go all the way to the top of the page again, *then* scroll, it fails to follow. Go to the top again, scroll again, it does. It quite literally appears 50 percent of the time ;p
Comment 1 Ryan Kaldari 2012-04-27 20:01:36 UTC
I can reproduce this every once in a while in Firefox. It does seem to have something to do with returning to the very top of the page after scrolling.
Comment 2 Ryan Kaldari 2012-05-01 00:14:05 UTC
This bug is very frustrating. Apparently, every once in a while...

$( '#mwe-pt-list-control-nav' ).parent().addClass('stickyTop');

just fails silently. No idea why.
Comment 3 Ryan Kaldari 2012-05-01 00:28:34 UTC
Seems to be a Firefox bug. If I activate the Javascript debugger in Firefox, it works without fail, but if the debugger is turned off, it's unreliable. Probably related to Firefox's weird JS thread handling.
Comment 4 Ryan Kaldari 2012-05-01 02:17:07 UTC
Tracked it down to a concurrency problem. Fixed in https://gerrit.wikimedia.org/r/#change,6221 by reworking the top waypoint function and adding some sanity checks.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links