Merge lp://staging/~osomon/webbrowser-app/historyUpdateOnLoadCommitted into lp://staging/webbrowser-app
- historyUpdateOnLoadCommitted
- Merge into trunk
Status: | Merged |
---|---|
Approved by: | Olivier Tilloy |
Approved revision: | 1029 |
Merged at revision: | 1372 |
Proposed branch: | lp://staging/~osomon/webbrowser-app/historyUpdateOnLoadCommitted |
Merge into: | lp://staging/webbrowser-app |
Diff against target: |
391 lines (+229/-40) 6 files modified
src/app/webbrowser/Browser.qml (+29/-2) src/app/webbrowser/history-model.cpp (+37/-1) src/app/webbrowser/history-model.h (+2/-1) tests/autopilot/webbrowser_app/tests/http_server.py (+32/-1) tests/autopilot/webbrowser_app/tests/test_history.py (+80/-34) tests/unittests/history-model/tst_HistoryModelTests.cpp (+49/-1) |
To merge this branch: | bzr merge lp://staging/~osomon/webbrowser-app/historyUpdateOnLoadCommitted |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Riccardo Padovani (community) | Approve | ||
PS Jenkins bot | continuous-integration | Needs Fixing | |
Ubuntu Phablet Team | Pending | ||
Review via email: mp+259361@code.staging.launchpad.net |
Commit message
Store entries in the history database on load committed, not load succeeded.
This ensures that content-initiated navigations are also stored.
Description of the change
PS Jenkins bot (ps-jenkins) wrote : | # |
PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1018
http://
Executed test runs:
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
Riccardo Padovani (rpadovani) wrote : | # |
+ browser.
Why this and not
browser.
?
I mean, we're updating the database, it's better to do it with last data we have, isn't it?
Olivier Tilloy (osomon) wrote : | # |
> + browser.
> webviewInternal
>
> Why this and not
>
> browser.
>
> ?
>
> I mean, we're updating the database, it's better to do it with last data we
> have, isn't it?
Some pages dynamically update the title to convey live information (like the ugly "scrolling title" effect, see e.g. http://
This is consistent with how chromium on desktop behaves.
Riccardo Padovani (rpadovani) wrote : | # |
Looks good to me now :-)
PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1019
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1020
http://
Executed test runs:
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1020
http://
Executed test runs:
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1020
http://
Executed test runs:
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
FAILURE: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1020
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
- 1021. By Olivier Tilloy
-
Merge the latest changes from trunk and resolve conflicts.
- 1022. By Olivier Tilloy
-
Add an update(…) method to HistoryModel, to allow updating the title and icon of an entry without incrementing the corresponding number of visits.
PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1022
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
- 1023. By Olivier Tilloy
-
Simplify code a bit.
Do not prevent dynamic favicon updates from updating the history database, to be consistent with what chromium does.
PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1023
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
- 1024. By Olivier Tilloy
-
Add some autopilot tests to verify that favicons are stored and updated in the history database.
- 1025. By Olivier Tilloy
-
Factor out common code.
- 1026. By Olivier Tilloy
-
Add autopilot tests to verify that a page’s title is stored in history, but not dynamically updated.
PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1025
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
- 1027. By Olivier Tilloy
-
Add an autopilot test to verify that history.pushState() inserts a new entry in the history database.
PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1026
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1027
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
Riccardo Padovani (rpadovani) wrote : | # |
I only read the code and seems good to me, just a couple of very little improvements inline.
I'll test asap.
- 1028. By Olivier Tilloy
-
Swap the order in which conditions are evaluated, from cheapest to most expensive.
- 1029. By Olivier Tilloy
-
Move code out of else block to avoid compiler warning (control reaches end of non-void function [-Wreturn-type]).
Olivier Tilloy (osomon) wrote : | # |
Thanks, those were very good points, I addressed them.
PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1029
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
Riccardo Padovani (rpadovani) wrote : | # |
Thanks! Tested a bit and seems to work like a charm.
FAILED: Continuous integration, rev:1017 jenkins. qa.ubuntu. com/job/ webbrowser- app-ci/ 1778/ jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- vivid-touch/ 2861/console jenkins. qa.ubuntu. com/job/ webbrowser- app-vivid- amd64-ci/ 535 jenkins. qa.ubuntu. com/job/ webbrowser- app-vivid- armhf-ci/ 535 jenkins. qa.ubuntu. com/job/ webbrowser- app-vivid- armhf-ci/ 535/artifact/ work/output/ *zip*/output. zip jenkins. qa.ubuntu. com/job/ webbrowser- app-vivid- i386-ci/ 535 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- runner- vivid-mako/ 2451/console jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 2859 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 2859/artifact/ work/output/ *zip*/output. zip s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 20559
http://
Executed test runs:
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/webbrowser- app-ci/ 1778/rebuild
http://