Closed Bug 745875 Opened 12 years ago Closed 12 years ago

Drawer sometimes gets "stuck" and won't scroll if page list is longer than the screen

Categories

(Pancake Graveyard :: Front-end, defect)

Product:
Pancake Graveyard
Component:
Front-end
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: deb, Assigned: gbrander)

Details

I've seen this when browsing around Reddit and CBC.ca a lot -- I'll start on the home page of one of these sites, then click a link, then back to the home page, etc...flipping back to the home page a bunch of times. Eventually the page list gets long enough that I'll need to scroll down to the bottom to find the home page again. The problem is that scrolling sometimes breaks in this situation -- A new page will be added to the top of the stack, but things get stuck and I can't scroll down at all. To fix this i have to flip back to the Stacks list then back into the Reddit or CBC stack & scrolling will work again.
Also, sometimes it will scroll, but not all the way to the bottom.
I thught this was a native gesture thing but I put together a long list of stacks and a stack with many items and it is just the contents of a stack that does not scroll. Pretty consistently when flpping back and forth, opening a stack and going back to the stack list.
Still seeing this -- going to mark as M3 for now.
Target Milestone: --- → M3
Assignee: nobody → gbrander
This may be related to height fixing that happens when panning between drawers. Investigate.
We recalculate the height of the drawer when switching between panes, but not when adding a new stack/place to the drawer. This means that after adding a place, the last place or stack can get cut off.
We're rendering the height via activateChild, not on the view itself. We crop the panel with a wrapping div that is outside of the panel view. One approach: make the drawer a widget view, require the relevant collections be passed in and change height based on collection events.
You need to log in before you can comment on or make changes to this bug.