Gaia/Browser: Difference between revisions

no edit summary
No edit summary
Line 4: Line 4:
* Feature Name: Gaia Browser App
* Feature Name: Gaia Browser App
* Stage: Development
* Stage: Development
* Release Target: [https://wiki.mozilla.org/B2G/Roadmap#Milestone_2:_Product_Demo_Q1_2012 B2G Demo Phone], Q1 2012
* Release Target: [https://wiki.mozilla.org/B2G/Roadmap#Milestone_2:_Product_Demo_Q1_2012 M2 - B2G Demo Phone], Q1 2012


== Team ==
== Team ==
Line 15: Line 15:


== Issues & Risks ==
== Issues & Risks ==
* [https://github.com/andreasgal/gaia/issues/25 Browser content doesn't scroll with touch events]
* <strike>[https://github.com/andreasgal/gaia/issues/25 Browser content doesn't scroll with touch events]</strike>
* Need to make popup windows (e.g. alert, authentication and window.open) work {{bug|716664}}
* Need to make popup windows (e.g. alert, authentication and window.open) work {{bug|716664}}
** window.open should now work {{bug|721777}}
** window.open should now work {{bug|721777}}
* Need a better solution for ignoring X-Frame-Options headers for <iframe mozbrowser> elements (B2G currently just has a pref which disables them for whitelisted domains)
* Need a better solution for ignoring X-Frame-Options headers for <iframe mozbrowser> elements (B2G currently just has a pref which disables them for whitelisted domains)
* Find a way to use the iframe's window.history instead of having to re-implement the history API inside the app. (some discussion in {{bug|708179}})
* Find a way to use the iframe's window.history instead of having to re-implement the history API inside the app. (some discussion in {{bug|708179}})
* Window.top should stop at the iFrame to prevent parent navigation & frame busting ({{bug|704037}})
* Some UX Unknowns (see Design section)
* Some UX Unknowns (see Design section)
* Window.top should stop at the iFrame to prevent parent navigation & frame busting ({{bug|704037}})


== Definition ==
== Definition ==
=== User Stories ===
=== User Stories ===
==== M2 - Demo Phone ====
* [https://github.com/andreasgal/gaia/issues/61 Navigate to URL]
* [https://github.com/andreasgal/gaia/issues/61 Navigate to URL]
* [https://github.com/andreasgal/gaia/issues/62 Back & Forward]
* [https://github.com/andreasgal/gaia/issues/62 Back & Forward]
* [https://github.com/andreasgal/gaia/issues/181 Stop]
* [https://github.com/andreasgal/gaia/issues/63 Reload]
* [https://github.com/andreasgal/gaia/issues/63 Reload]
* [https://github.com/andreasgal/gaia/issues/288 Browser Title & URL Update on Navigate]
* [https://github.com/andreasgal/gaia/issues/288 Browser Title & URL Update on Navigate]
==== M3 - Product ====
* [https://github.com/andreasgal/gaia/issues/181 Stop]
* [https://github.com/andreasgal/gaia/issues/66 New Tab]
* [https://github.com/andreasgal/gaia/issues/66 New Tab]
* [https://github.com/andreasgal/gaia/issues/67 Switch Tab]
* [https://github.com/andreasgal/gaia/issues/67 Switch Tab]
Line 50: Line 53:


[[Image:gaia_browser_menu_mockup-m2.png]]
[[Image:gaia_browser_menu_mockup-m2.png]]
Some open questions for the browser design post-M2:
* Whether to implement bookmarks at the browser level or at the homescreen level
* Whether to move tab management to the homescreen level
* Whether there should be an "awesomescreen" at the browser level or the homescreen level [https://wiki.mozilla.org/B2G/UI#Ben.27s_Gaia_Concept here]


== Development ==
== Development ==
[https://github.com/andreasgal/gaia/tree/master/apps/browser Source code on Github]
[https://github.com/andreasgal/gaia/tree/master/apps/browser Source code on Github]
Confirmed users
394

edits