On Thursday, October 22, 2015 at 7:13:21 AM UTC-4, Michael Henretty wrote: > On Wed, Oct 21, 2015 at 7:01 PM, Andrew Sutherland <[email protected]> > wrote: > > Can you clarify what you mean by "bring back the browser chrome"? > > > > I'm talking about the second case you mentioned, opening Firefox OS "apps." > By default there is no way to access the browser navigation chrome (beyond > using the search bar). Having that as default behavior (and indeed the > behavior in all Gaia apps) clearly shows our intent that FxOS "apps" should > implement their own navigation. Is this the right approach? Certainly we need > to give developers choice, but for instance not having the back button on > FxOS "apps" like Facebook can make the navigation experience unnecessarily > frustrating. Facebook works much better as a pin IMO :) > > I don't think we want the web #2 [expanding/collapsing chrome on scroll] > 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.) > > > Fennec, mobile chrome, and mobile safari all expand/collapse chrome on > scrolling in some way. I agree it can be a little annoying, but the extra > screen real estate is also extremely useful. In any case, I don't think > scrollgrab is confusing to users since it has become somewhat of a standard. > But it's definitely useful to discuss alternative approaches. > > > More generally though, I agree that having URL-based navigation and making > single-paged apps are two separate topics. Sorry if I conflated the two. > Let's drop the single-page app part since it's orthogonal to this discussion. > > It seems like we all agree we want URL based navigation. It also seems the we > *mostly* agree that the android back button is a tad unpredictable and we > shouldn't fully emulate them. So the question remains here about > disposition, and best practices we encourage with Gaia apps. Developer choice > aside (which we should obviously keep), should Gaia apps be leveraging > browser chrome (back, forward, refresh, pin, share, etc)?
Cant we use the edge swipe functionality to trigger backbutton event? I think that would be a better option than actually adding a visible back button at the bottom. I love firefox OS because of its simplicity and its home button. A single button at the bottom of the screen makes it look beautiful, so adding an extra back button is something that would definitely not look good. _______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
