Merge lp:~ivaldi/midori/drop-notify-uri into lp:midori
Proposed by
André Stösel
Status: | Merged |
---|---|
Approved by: | Cris Dywan |
Approved revision: | 6313 |
Merged at revision: | 6331 |
Proposed branch: | lp:~ivaldi/midori/drop-notify-uri |
Merge into: | lp:midori |
Diff against target: |
27 lines (+0/-10) 1 file modified
midori/midori-view.c (+0/-10) |
To merge this branch: | bzr merge lp:~ivaldi/midori/drop-notify-uri |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Cris Dywan | Approve | ||
gue5t gue5t | Approve | ||
Review via email: mp+178436@code.launchpad.net |
Commit message
Drop redundant notify::uri handler
Description of the change
midori_tab_set_uri is called twice on every uri change
first in "midori_
since there is one special case handled in "midori_
To post a comment you must log in.
I like the idea of removing duplicate code (and the patch itself is fine mechanically) but this makes me wary. I'd like to see either some testing (e.g. logging and examining exactly when the different codepaths get called in the course of browsing), history-digging (when and why did we end up with two codepaths for the same thing?), or webkit source code justifications to ensure that this doesn't change behavior in a subtle but buggy way. I realize I sound pretty harsh here but in my opinion details of when tab uris are set is an area in which I think discipline is warranted.
Or hopefully I'm not misunderstanding the description: did you already test before/after this a fair bit, and find load_committed to suffice to provide the same behavior even in cases where pages are interrupted (user hits stop), take ages to time out, or fail to load?
Sorry to rain on any parades, this is just the kind of thing where webkit docs aren't always clear and we would do really well to make sure we have it right. :)