On Wed, Oct 21, 2015, at 08:30 AM, Michael Henretty wrote: > So I write this email today as sort of an opinion poll. Personally, I think > it's time we bring back the browser chrome into Firefox OS apps. I think we > should encourage developers to write URL-based apps, to not be afraid of > browser chrome navigation, and therefore to build their Firefox OS app as a > standard website + some experimental (or proprietary :/) APIs.
Can you clarify what you mean by "bring back the browser chrome"? Right now if I open https://mobile.twitter.com in the FxOS browser, I get two behaviors as it relates to browser chrome: 1) Tapping on the rocketbar bubble in the status bar at the top expands the "[back] ([favicon][lock icon] current-domain [refresh]) [hamburger]" chrome. 2) Scrolling up cause the rocketbar bubble to expand in the same way, scrolling down causes it to go away. And if I open the same site in our app frame, instead: 1) Tapping on the rocketbar expands it and transitions to the "(last thing I typed [x] Close)" search overlay, with no ability to impact the current application. 2) Scrolling up or down does not cause the rocketbar to expand. I think it would be great to get the web #1 case, where tapping on the rocketbar causes it to expand and let me know what I'm looking at and be able to bookmark and do other actions related to the current app other than jumping to global web search[1]. I don't think we want the web #2 case. (I'm not sure the web even wants it; Fennec does the scrollgrab thing because it can't insert a rocketbar-like capsule in the status bar that responds to tapping.) Back-button-wise, that seems like a separate issue. I agree with everyone who is saying they don't want the app to give up screen real- estate for the back button feature that they would otherwise have. I think these are all viable affordances: - Having it in the rocketbar that expands *only when you tap on it* - Our edge swipe gestures that we already have. - Putting it in the "soft home button" strip at the bottom. - Using any existing hardware back button that exists for Android-ish devices that don't use a soft home button. Andrew 1: For example, we could use our awesomebar-equivalent to provide hot- links to frequently visited URLs within the app without the user having to type everything. Like if you've web-pinned your "dev-fxos" label/folder in the email app, or just visit it a lot, that could be displayed as a tappable navigation bubble item.
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
