Closed Bug 929728 Opened 11 years ago Closed 11 years ago

Add a setting to enable APZC in all of gaia

Categories

(Firefox OS Graveyard :: Gaia, defect)

All
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kats, Assigned: kats)

References

Details

Attachments

(1 file, 1 obsolete file)

APZC can be turned on in all gaia apps now, but there are some issues in various apps that need to be fixed (see some of the other bugs blocking 909877). In order to allow gaia developers to more easily investigate these problems, Vivien suggested adding a debug option to enable APZC everywhere.

Patches incoming.
Note that only apps that are created *after* checking the box will have the APZC enabled. You will need to restart b2g to enable APZC on the homescreen app.
Comment on attachment 820629 [details] [diff] [review]
Part 1 - Gecko patch to read and apply the settings change

Review of attachment 820629 [details] [diff] [review]:
-----------------------------------------------------------------

Instead of having both a Gecko patch and a Gaia patch you can do all the work in Gaia.

Just add a SettingsListener in apps/system/js/browser_frame.js that toggle a global variable (for this file) that force the 'asyncpanzoom' attribute to be set.
Attachment #820629 - Flags: review?(21)
Attachment #820629 - Attachment is obsolete: true
Comment on attachment 820631 [details] [review]
Change to gaia settings app

Updated to be all in gaia. I assume it's expensive to call SettingsListener.getSettingsLock().get(apzSetting) otherwise I could just do that on every frame creation instead of storing a local variable.
Attachment #820631 - Attachment description: Part 2 - Change to gaia settings app → Change to gaia settings app
Attachment #820631 - Flags: review?(21)
Comment on attachment 820631 [details] [review]
Change to gaia settings app

Can you add a comment explaining that it is temporary?

Also it is not really expensive, but just async so that would delay frames creation.
Attachment #820631 - Flags: review?(21) → review+
I updated the PR with the comment. I also noticed that the travis-CI build ran on my PR and failed the unit tests for browser_frame.js. I patched that up too but I haven't been able to verify that my fixes to that work - the travis CI failed for some unrelated reason it looks like, and I haven't been able to successfully run the tests locally.
I re-pushed the PR and the unit test for browser_frame.js is still failing. I need to figure out how to run the test locally so I can fix it without round-tripping through travis all the time.
Comment on attachment 820631 [details] [review]
Change to gaia settings app

Ok, with Rik's help I was able to repro the failure locally and fix it. The fix was a little more involved than I thought it would be, but I tried to make it as elegant as I could. PR is updated with the fix, but re-requesting review since the fix to the test was nontrivial.

Feel free to merge the PR if the travis run is green and you're fine with the changes I made.
Attachment #820631 - Flags: review?(21)
Attachment #820631 - Flags: review+
Attachment #820631 - Flags: feedback+
Attachment #820631 - Attachment is patch: true
Attachment #820631 - Attachment mime type: text/x-github-pull-request → text/plain
Attachment #820631 - Attachment is patch: false
Attachment #820631 - Attachment mime type: text/plain → text/x-github-pull-request
The travis run failed but for what looks like an unrelated thing.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: