Closed Bug 957077 Opened 10 years ago Closed 10 years ago

Tweetdeck panels stop rendering and/or disappear in Metro mode

Categories

(Core :: Panning and Zooming, defect)

x86
Windows 8.1
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: cwiiis, Unassigned)

References

Details

(Whiteboard: [metro] [gfx])

If you switch the browser to Windows 8 mode and visit tweetdeck.twitter.com (of course, with an account setup and multiple panels configured), after scrolling some of the panels, they tend to stop re-rendering (they still respond to input, but the display doesn't change), and sometimes just disappear entirely.

This is likely an APZC-related layout bug.
Whiteboard: [triage] [defect] p=0
Kats, could you take a look and see if this is indeed an APZC bug?  We'd like to know whether we should block release on this.
Component: Browser → Panning and Zooming
Flags: needinfo?(bugmail.mozilla)
Product: Firefox for Metro → Core
Whiteboard: [triage] [defect] p=0 → [metro] [triage] [defect] p=0
Version: unspecified → Trunk
Whiteboard: [metro] [triage] [defect] p=0 → [metro] [triage] [gfx]
Selfishly, I'd like this to block release because I use Tweetdeck all the time :) Slightly less selfish reasoning, Tweetdeck isn't a particularly complex or uncommon arrangement, structurally, and I'd be surprised if this bug didn't manifest quite commonly elsewhere (but perhaps on less critical content).
Chris, can you extract a standalone/simplified test case for this? I'd rather not have to create a tweetdeck account if I don't have to. Even if the test case isn't simplified but is a "File -> Save As..." snapshot of the page that demonstrates the problem that would help.
Needinfo'ing myself for comment #3
Flags: needinfo?(chrislord.net)
I tried to reproduce this but was unable to. I signed in to tweetdeck using my twitter credentials and scrolled around in the four panels that show up by default (home/notifications/messages/activity) using touch scrolling. I saw some checkerboarding (i.e. flashes of white) but nothing else obviously wrong.

Chris, if you can repro getting a log with the APZC logging turned on (the defines at the top of APZCTreeManager.cpp and AsyncPanZoomController.cpp) would be helpful. Or you could debug it since you know the code well enough :)
Flags: needinfo?(bugmail.mozilla)
The bug only manifests after scrolling horizontally, so you may need to add more columns - I could still reproduce this a couple of days ago. The only difficulty is I don't have a windows machine handy to build right now, is there a way to enable APZC in Linux?

I'll see about getting a reduced test case. Also worth noting, a new bug has cropped up where you can't scroll horizontally if you initiate the scroll from one of the vertically scrolling columns.
Is this maybe a dupe of bug 956690?
(In reply to Jim Mathies [:jimm] from comment #7)
> Is this maybe a dupe of bug 956690?

They could well be related, but I think if that is the cause, there are some very incorrect displayports being set...
Whiteboard: [metro] [triage] [gfx] → [metro] [gfx]
Clearing my needinfo and resolving as I'm pretty sure this is fixed now.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(chrislord.net)
Resolution: --- → INCOMPLETE
No longer blocks: metrobacklog
You need to log in before you can comment on or make changes to this bug.