Description of problem: This is a problem on all bugzilla instances, but works fine in midori --plain. To reproduce: Visit <http://bugzilla.kernel.org/>. Enter "a" in the search box at top, and hit enter. A "Save/Save as/Open/Cancel" dialog will open, instead of the desired page. In addition, selecting "Open" will result in Midori's memory usage increasing without bound. Version-Release number of selected component (if applicable): midori-0.5.8-1.fc20.x86_64 How reproducible: yes Steps to Reproduce: $ midori https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__&content=a&list_id=2810345&order=relevance%20desc&product=Fedora&query_format=specific Actual results: Download dialog opens. Expected results: Some search result page should be shown. Additional info: Midori truncates the URL, so the server can not get the original request. Upstream is aware of the issue: https://bugs.launchpad.net/midori/+bug/1365225
An Arch user and midori developers say that it's not reproducible with WebkitGtk 2.4.x, though 2.2.x seems to truncate the URL. Rawhide 2.4.5-3.fc22 Fedora 21 2.4.5-1.fc21 (2.4.5-2.fc21 in testing) Fedora 20 2.2.7-3.fc20 Can we get webkitgtk 2.4.x also for F20 for a chance to fix this issue?
So, this is a webkitgtk issue right? Not sure what good this bug is... should we keep it open for some reason? Or just track this in 1139039?
(In reply to Kevin Fenzi from comment #2) > So, this is a webkitgtk issue right? Not sure what good this bug is... Webkit -> URL truncation Midori -> fails to load the search result page, this seems to independet from the wrong URL in address bar. > should we keep it open for some reason? Or just track this in 1139039? Please keep it open due to the upstream bug. Have a look also to my comments there in the upstream tracker. As a developer said, the download dialog is because of a false mime type detection, besides the recognized URL is wrong generally. So my suggestion: Wait for upstream to provide patches. Maybe Webkit can be fixed with a patch from upstream as some backport? All in all, we are talking about at least three bugs (for upstreams).
Okay, this does not depend on WebkitGtk. $ midori --version Midori 0.5.8 ((null)) Midori GTK+ 2.24.22 (2.24.24) Glib 2.38.2 (2.38.2) WebKitGTK+ 2.2.6 (2.4.5) libSoup 2.44.2 cairo 1.13.1 (1.13.1) libnotify 0.7.6 gcr No granite No
Midori 0.5.8 ((null)) Midori GTK+ 2.24.22 (2.24.24) Glib 2.38.2 (2.38.2) WebKitGTK+ 2.2.6 (2.2.8) libSoup 2.44.2 cairo 1.13.1 (1.13.1) libnotify 0.7.6 gcr No granite No