Closed
Bug 559437
Opened 14 years ago
Closed 13 years ago
Panning images inside overflow:auto elements (Google Reader) stops for some posts
Categories
(Firefox for Android Graveyard :: Panning/Zooming, defect, P1)
Firefox for Android Graveyard
Panning/Zooming
Tracking
(fennec2.0+)
RESOLVED
DUPLICATE
of bug 618975
Tracking | Status | |
---|---|---|
fennec | 2.0+ | --- |
People
(Reporter: whimboo, Assigned: stechz)
References
()
Details
(Keywords: qablocker, testcase)
Attachments
(1 file)
644 bytes,
text/html
|
Details |
If a feed entry on Google Reader contains a big images no panning is possible. You can only try to pan the small empty border on the left side. But that's not the way it should work. Panning on the image should be possible. Looks like it's also related to overflow:auto? Steps: 1. Subscribe to http://djst.org/blog/feed/ 2. Search for "Silicon Valley" from March 1st 3. Open the post and try to scroll down
Comment 1•14 years ago
|
||
Can you mention what build id you're using, henrik?
Comment 2•14 years ago
|
||
I love how my blog is unique enough to serve as multiple test cases. It's not just my fantastic writing style, I guess!
Comment 3•14 years ago
|
||
In this case, it's impossible to vertically scroll the red bordered block, from inside the blue bordered box.
Comment 4•14 years ago
|
||
Matthew fixed bug 556414, so he might have a clue why this isn't working.
Keywords: testcase
Comment 5•14 years ago
|
||
I think this is because we stop looking for scrollable elements as soon as we find one. If two scrollable elements are nested, only the inner one will scroll. Keyboard scrolling in desktop Firefox has the same problem. (Click inside the red box in the testcase and use the arrow keys to scroll.) To fix this we will need to build a chain of scrollable elements and walk through them with Browser._panScroller (like we do for the nested scrollboxes in the Fennec chrome).
Updated•14 years ago
|
Updated•14 years ago
|
tracking-fennec: 2.0b1+ → 2.0b2+
Updated•14 years ago
|
Priority: -- → P1
Updated•14 years ago
|
tracking-fennec: 2.0b2+ → 2.0b3+
Updated•14 years ago
|
tracking-fennec: 2.0b3+ → 2.0b4+
Updated•14 years ago
|
tracking-fennec: 2.0b4+ → 2.0+
Assignee | ||
Comment 6•14 years ago
|
||
Work for this is currently being done in bug 618975.
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•