Closed
Bug 997269
Opened 10 years ago
Closed 6 years ago
Scrolling up on python docs makes the menu jump up and down
Categories
(Web Compatibility :: Site Reports, defect, P3)
Web Compatibility
Site Reports
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: Pike, Unassigned)
References
()
Details
(Keywords: polish, Whiteboard: [gfx-noted][apz-evangelism] [sitewait])
Attachments
(1 file)
1.87 MB,
video/webm
|
Details |
I'm attaching a screencast. Go to https://docs.python.org/2/library/logging.html#handler-objects, and scroll up. Once the index reaches the top, it starts jumping up and down. No idea why, I've got to the point that it's a float with position: relative, and top is adjusted dynamically. It works fine for me on 28, I see it on Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0), BuildID is 20140416030202.
Based on the description from the reporter, changing status to RESOLVED WORKS FOR ME. Tested on Windows 7 x64 with the Nightly 46.0a1 build. I can't reproduce the problem. Please reopen the bug if you encounter this issue again. Thank you.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 2•8 years ago
|
||
Maybe OSX specific, just reproduced on Nightly on El Capitan.
Status: RESOLVED → REOPENED
OS: All → Mac OS X
Resolution: WORKSFORME → ---
Hello. I retested the problem on Windows 7 x64 and MacOS El Capitan on the Firefox Nightly and the issue reproduces. I also tested it on Chrome and IE and the behaviour is the same. I used the moz-regression tool. On mozilla-inbound, the last good build is: pushlog_url: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=f1fd6e8e6b43147fc4071594788f0068b0d68953&tochange=af67b5f73381f154f41ded5926d823709a0ebd08 On mozilla-inbound, the first bad build is: pushlog_url: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=1413ee039b51890170c52e49cf539a8e3ab6f758&tochange=af67b5f73381f154f41ded5926d823709a0ebd08
Status: REOPENED → NEW
Component: Untriaged → Graphics
OS: Mac OS X → All
Product: Firefox → Core
Reporter | ||
Comment 4•8 years ago
|
||
The APZ landing is in the second push? CCing kats.
Comment 5•8 years ago
|
||
They're updating the transform on scroll events, which isn't going to work so well with APZ. As mentioned in comment 3 Chrome has the same issue, we need to reach out to the site maintainers and ask them to not do that. Using position:fixed or position:sticky would be better here.
Reporter | ||
Comment 6•8 years ago
|
||
Seems that https://bugs.python.org/issue24712 is the upstream ticket.
Comment 7•8 years ago
|
||
Thanks for finding that; I posted a comment to that bug pointing back here and with some additional info. Also I just noticed that this bug was filed in April 2014 which was before we had APZ on desktop, so I don't know if the original issue you saw (comment 0) had the same root cause. Regardless, it's now happening because of APZ.
Comment 8•8 years ago
|
||
We possibly need to get the fix done a the Spyhnx level, then ask Python to update their version: http://www.sphinx-doc.org/en/stable/. Both the Python 2.x docs and Python 3 are generated with Sphinx 1.3.3, but the 3 docs don't have the same issue (they have a static TOC in the sidebar). So it's possible the problem is python.org specific (if it's not some packaged theme). To investigate.
Comment 9•8 years ago
|
||
This is probably the right place to file issues/send patches: https://github.com/python/pythondotorg/issues
Comment 10•8 years ago
|
||
Python just moved to Github. http://www.snarky.ca/the-history-behind-the-decision-to-move-python-to-github As Mike said the docs pages are generated through Sphinx. The driver script is at https://github.com/python/docsbuild-scripts/blob/master/build_docs.py#L79 Documentation bugs are listed at https://bugs.python.org/issue?@filter=status&@filter=components&components=4&status=1&@columns=id,activity,title,status&@sort=-activity Mike's link is about python.org Web site and not the Python Docs Web site ;) The documentation RST files are at https://github.com/python/cpython/tree/master/Doc The documentation documentation (whiiiz) is https://docs.python.org/devguide/documenting.html And if there is an issue with the sidebar maybe someone could prepare a Pull Request on https://github.com/python/cpython/blob/master/Doc/tools/static/sidebar.js Specifically the part they call https://github.com/python/cpython/blob/master/Doc/tools/static/sidebar.js#L165 /* intelligent scrolling */ function scroll_sidebar() { }
Flags: needinfo?(miket)
Updated•8 years ago
|
Whiteboard: [apz-evangelism] → [apz-evangelism] [needsPR]
Comment 11•8 years ago
|
||
Karl, you're amazing. Leaving ni? on myself -- I'll take a stab at a PR.
Updated•8 years ago
|
Keywords: polish
Whiteboard: [apz-evangelism] [needsPR] → [gfx-noted][apz-evangelism] [needsPR]
Comment 12•8 years ago
|
||
I'm moving apz-evangelism bugs that are ready for attention by the Tech Evangelism team (or already in the process of getting it) into the Tech Evangelism component.
Component: Panning and Zooming → Desktop
Product: Core → Tech Evangelism
Comment 13•8 years ago
|
||
Sorry for taking ages on this. Just submitted a patch to the Python project: http://bugs.python.org/issue24712#msg265950
Flags: needinfo?(miket)
Whiteboard: [gfx-noted][apz-evangelism] [needsPR] → [gfx-noted][apz-evangelism] [sitewait]
Comment 14•8 years ago
|
||
(In reply to Mike Taylor [:miketaylr] from comment #13) > Just submitted a patch to the Python project: > http://bugs.python.org/issue24712#msg265950 Is there someone we could ping to get this reviewed / committed?
Comment 15•8 years ago
|
||
Karl pinged in the bug, hopefully that has the right effect!
Updated•6 years ago
|
Priority: -- → P3
Comment 16•6 years ago
|
||
This is still reproducible on Windows 10 and Firefox Nightly 63.
Comment 17•6 years ago
|
||
The updated theme for Python 3 is working as expected. Closing as wontfix.
Status: NEW → RESOLVED
Closed: 8 years ago → 6 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•5 years ago
|
Product: Tech Evangelism → Web Compatibility
You need to log in
before you can comment on or make changes to this bug.
Description
•