webbrowser-app

[browser] webapps should have the chrome bar with only back & forward buttons enabled

Bug #1116412 reported by Oren Horev
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Ubuntu UX
Fix Released
High
Oren Horev
webbrowser-app
Fix Released
High
Olivier Tilloy
webbrowser-app (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

When navigating a web app there are cases in which the web page developers assumed browser navigation is available. In those cases having the ability to swipe in the chrome bar with a back and forward buttons stands for a better web apps UX.

At the least, if the described solution is not feasible chrome bar with a disabled url box should be enabled.

See original description
Tags: phone tablet
Oren Horev (oreneeshy)
tags: added: phone tablet
summary: - [Browser] Webapps should have the chrome bar by default with url box
- disabled
+ [Browser] Webapps should have the chrome bar by default with back button
summary: - [Browser] Webapps should have the chrome bar by default with back button
+ [Browser] Webapps should have the chrome bar with back button only by
+ default
summary: - [Browser] Webapps should have the chrome bar with back button only by
- default
+ [Browser] Webapps should have the chrome bar with back & forward buttons
+ only by default
summary: - [Browser] Webapps should have the chrome bar with back & forward buttons
- only by default
+ [Browser] Webapps should, by default have the chrome bar with only back
+ & forward buttons enabled
summary: - [Browser] Webapps should, by default have the chrome bar with only back
- & forward buttons enabled
+ [Browser] By default webapps should have the chrome bar with only back &
+ forward buttons enabled
summary: - [Browser] By default webapps should have the chrome bar with only back &
- forward buttons enabled
+ [Browser] By default, webapps should have the chrome bar with only back
+ & forward buttons enabled
description: updated
description: updated
Oren Horev (oreneeshy)
description: updated
description: updated
Tony Espy (awe)
Changed in manhattan:
status: New → Confirmed
importance: Undecided → High
Olivier Tilloy (osomon)
summary: - [Browser] By default, webapps should have the chrome bar with only back
- & forward buttons enabled
+ [browser] webapps should have the chrome bar with only back & forward
+ buttons enabled
Revision history for this message
Oren Horev (oreneeshy) wrote :

we need to add a refresh button as well to a webapp toolbar - so back, forward, refresh

Revision history for this message
Olivier Tilloy (osomon) wrote :

We’ll need to add a new command line switch, something like "--webapp". At the moment, the assumption is that webapp == chromeless.
I guess we don’t necessarily need to get rid of the chromeless mode (it could prove useful in some use cases), but we need to invalidate this assumption.

Alan Pope 🍺🐧🐱 🦄 (popey)
information type: Proprietary → Public
affects: manhattan → webbrowser-app
Revision history for this message
Adnane Belmadiaf (daker) wrote :

I think this is no a good idea, the only thing that let the user know if the page is the correct page and not a pishing page/if we are using an encrypted connexion(https) or not is the addressbar.

Oren Horev (oreneeshy)
Changed in ubuntu-ux:
status: New → Fix Committed
importance: Undecided → High
assignee: nobody → Oren Horev (oreneeshy)
Revision history for this message
Vincent (vinnl) wrote :

This is a website problem, not a browser problem. Websites shouldn't assume browser navigation to be available. If need be, website developers should be able to check for location bar visibility through window.locationbar.visible: https://developer.mozilla.org/en-US/Apps/FAQs/About_apps#How_can_my_app_detect_that_it_is_in_the_Web_runtime.3F

Revision history for this message
Olivier Tilloy (osomon) wrote :

Marking fixed in the browser: some command-line switches were added so that webapps can launch the browser with the amount of chrome they need. Which switches to activate is decided in the webapps’ desktop files.

Changed in webbrowser-app:
status: Confirmed → Fix Released
Changed in webbrowser-app (Ubuntu):
status: New → Fix Released
Revision history for this message
Basil Dobek (bdobek) wrote :

Does anyone know which specific switches were added to address this issue?

Revision history for this message
Olivier Tilloy (osomon) wrote :

@Basil: you can get a list of all available command line switches if you run the app with the -h/--help switch.
Here are the relevant options:

Chrome options (if none specified, the whole chrome is enabled by default):
  --chromeless do not display any chrome (web application mode), if set it overrides the other chrome options
  --enable-back-forward enable the display of the back and forward buttons
  --enable-activity enable the display of the activity button, the address bar is also displayed
  --enable-addressbar enable the display of the address bar

John Lea (johnlea)
Changed in ubuntu-ux:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.