Closed Bug 828210 Opened 12 years ago Closed 12 years ago

Workaround bug 825622 in Gaia

Categories

(Firefox OS Graveyard :: Gaia::Settings, defect, P2)

defect

Tracking

(blocking-basecamp:+)

RESOLVED FIXED
B2G C4 (2jan on)
blocking-basecamp +

People

(Reporter: rik, Assigned: rik)

References

(Depends on 1 open bug)

Details

(Keywords: b2g-testdriver, Whiteboard: [b2g-gfx])

Attachments

(1 file)

+++ This bug was initially created as a clone of Bug #825622 +++

STR:
 (can reproduce with: en-US, fr, pt-BR)
 - Tap Settings
 - Tap Device Information
 - Tap Legal information
 - Tap Open Source Notice

Seen:
 - Nothing happen, and a white screen show up after a short while.

Expected:
 - Start the browser app.


In this bug, we'll do a workaround in gaia while other people work on fixing the underlying bug 825622.
Assignee: nobody → rexboy
Assignee: rexboy → anthony
Moving to Gaia.  FYI:  we previously had this as a blocker on the platform which is why the flag is still set here.
Component: General → Gaia::Settings
Currently it does show the "Open Source Licensing Information" page after a "long" while.

Do we really expect it to start the browser app?
(In reply to Anthony Ricaud (:rik) from comment #0)
> +++ This bug was initially created as a clone of Bug #825622 +++
> 

Please update the summary when you clone bugs.

What's the proposed workaround here? Launch Browser app instead?
Summary: Tapping settings app UI while "Open Source Notice" is loading causes all-white window to be rendered after notice loads → Workaround bug 825622 in Gaia
According to the profile data, 96.% time is spent in layout::DoReflow
(In reply to Kan-Ru Chen [:kanru] from comment #4)
> According to the profile data, 96.% time is spent in layout::DoReflow

As said in bug 825622 :)
(In reply to Tim Guan-tin Chien [:timdream] (MoCo-TPE) from comment #3)
> What's the proposed workaround here? Launch Browser app instead?

Would we have the same rendering issue inside a browser tab? Maybe we need to paginate the content somehow?
My current workaround is to use an empty iframe and set the src after we transitioned and remove it when we leave the panel.

I'm also trying alternatives to remove the setTimeout() logic of panel switching but so far, it regresses the animation the first time we open a panel.
(In reply to Anthony Ricaud (:rik) from comment #7)
> My current workaround is to use an empty iframe and set the src after we
> transitioned and remove it when we leave the panel.
> 
> I'm also trying alternatives to remove the setTimeout() logic of panel
> switching but so far, it regresses the animation the first time we open a
> panel.

The regression of the animation is really not important imo... Having an application that works without having to kill it is way more important.
Not sure if anyone's considering this, but from a legal perspective, loading this page off the network rather than having it stored locally is a no-no. Just wanted to mention it :-)

Gerv
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Attachment #700033 - Flags: review?(kaze) → review+
Target Milestone: --- → B2G C4 (2jan on)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: