Closed Bug 916803 (app-chrome) Opened 8 years ago Closed 7 years ago
[Window Management] Use dynamic generated chrome UI (wrapper header/footer) instead of fixed one
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?
Do what you want to do but I'm afraid this is blocked by moving browser frame to app window bug.
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.
No longer blocks: task-manager
Bug 907013 would introduce an initial version of AppChrome. Need finetune here.
Fixed by 907013 landed
Status: NEW → RESOLVED
Closed: 7 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.