[webapp-container] Staging Regression: In staging the progress bar does not function within webapps
Bug #1633616 reported by
Andrew Hayzen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| webbrowser-app (Ubuntu) |
Confirmed
|
High
|
Unassigned | ||
Bug Description
What Happened:
1) Open a webapp, eg facebook or twitter
2) Watch the progress bar (the blue bar under the address at the top)
3) Notice that it does not move or disappear
What I expected to happen:
At step 3 for the progress bar to function correctly.
Note that this only happens on lp:webbrowser-app/staging (#1563) not trunk and only seems to happen within webapps not the browser.
Related branches
lp:~osomon/webbrowser-app/staging-fix-webapp-container-progress-bar
- Andrew Hayzen (community): Approve
- Alexandre Abreu (community): Approve
-
Diff: 12 lines (+3/-0)1 file modifiedsrc/app/webcontainer/Chrome.qml (+3/-0)
| summary: |
- [webapp-container] In staging the progress bar does not function + [webapp-container] Staging Regression: In staging the progress bar does + not function within webapps |
Revision history for this message
| Olivier Tilloy (osomon) wrote | #1 |
| Changed in webbrowser-app (Ubuntu): | |
| status: | New → Confirmed |
| importance: | Undecided → Critical |
| importance: | Critical → High |
| assignee: | nobody → Olivier Tilloy (osomon) |
| Changed in webbrowser-app (Ubuntu): | |
| status: | Confirmed → In Progress |
| Changed in webbrowser-app (Ubuntu): | |
| status: | In Progress → Confirmed |
| assignee: | Olivier Tilloy (osomon) → nobody |
To post a comment you must log in.
Interestingly, this is observable only when there is some chrome (i.e. when the webapp container is invoked with --enable-addressbar or --enable-