Closed Bug 916803 (app-chrome) Opened 6 years ago Closed 6 years ago

[Window Management] Use dynamic generated chrome UI (wrapper header/footer) instead of fixed one.

Categories

(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)

ARM
Gonk (Firefox OS)
defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: alive, Assigned: alive)

References

Details

I'd like remove the fixed wrapper-header/wrapper-footer from index.html and generate the UI based on app window config (manifest.chrome.navigation = true or it's a wrapperWindow) to dynamically load/inject chrome navigation UI into app window container.
@alive, 

I'd like try to use share/template.js for those chrome navigation UI, any concern for that?
Flags: needinfo?(alive)
Do what you want to do but I'm afraid this is blocked by moving browser frame to app window bug.
Flags: needinfo?(alive)
Also it is prematurate to do too much work on it right now since the wrapper stuff should evolve a lot with browser at the system app level and trying to merge the concept of e.me bookmarks/web page in some way.
We have some hints now: a spec about browserOS and lots of work shall be done to implement the proposed chrome navigation UI:
https://mozilla.app.box.com/s/s3xx046zxhxyxci971ur

I don't have time to look deeply though.
Component: Gaia::System → Gaia::System::Window Mgmt
No longer blocks: task-manager
Bug 907013 would introduce an initial version of AppChrome. Need finetune here.
Alias: app-chrome
Fixed by 907013 landed
Status: NEW → RESOLVED
Closed: 6 years ago
Depends on: app-window-manager
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.