This appears to have been fixed by switching to oxide, which is built on
the chromium content API, which seems to allocate the first few percents
of the progress to waiting for a response from the server, as desired.
** Changed in: webbrowser-app
Status: Confirmed => Fix Released
** Changed in: webbrowser-app (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1227777
Title:
[browser] No progress feedback while waiting for server to respond
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1227777/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
