Description of problem: Hotmail webmail service is unusable with midori. After login, the browser is stuck in an endless loop without ever rendering the message window. Version-Release number of selected component (if applicable): midori-0.0.21-1.fc10.x86_64 How reproducible: Always. Steps to Reproduce: 1. Log in to http://www.hotmail.com. Actual results: Browser window flickers, and progress bar alternates between 21% and 50% without ever completing the transaction. Expected results: Window is loaded and message windows appears in the browser. Additional info: For current midori built against WebKit-gtk-1.0.0-0.15.svn37790.fc10.x86_64, no entries are added to .xsession-errors. However, for locally built packages midori-0.1.1-1.fc10.x86_64 and WebKit-gtk-1.0.0-0.17.svn39790.fc10.x86_64, the behaviour is strictly identical but now, .xsession-errors is filled with entries "console message: http://gfx6.hotmail.com/mail/13.2.0260.1209/cmpt0.js @1: TypeError: Result of expression 'a.HTMLElement.prototype' [null] is not an object."
The same issue occurs for epiphany-2.24.1-3.fc10.x86_64 built locally against WebKit-gtk. It is thus a WebKit issue which occurs even for the latest nightly build r39903. Upstream bug is https://bugs.webkit.org/show_bug.cgi?id=22633 .
Btw, https://bugs.webkit.org is not available under "External Bugs". Could anybody take care of adding it?
Issue has evolved such that it is now possible to enter the Hotmail user account. However, it is neither possible to open a message in the inbox nor to open a different folder. All Javascript actions recognizable by a label "javascript:;" appearing at the bottom of the browser window are disabled. In an alternate browser like epiphany this works correctly. Installed packages from the "rawhide" tree include - midori-0.1.6-2.fc11.1.x86_64 - webkitgtk-1.1.6-1.fc11.x86_64 Btw, browser "safari" which is also based on WebKit allows to use Hotmail without any problem.
After moving to the WebKit engine, epiphany-2.27.3-1.fc12.x86_64 are affected as well.
For current "rawhide", there is some progress: - webkitgtk-1.1.14-3.fc12.x86_64 / midori-0.1.10-1.fc12.x86_64 [SUCCESS] - webkitgtk-1.1.14-3.fc12.x86_64 / epiphany-2.27.92-2.fc12.x86_64 [FAILURE] Now, if success depends on the frontend, this might finally not be a webkitgtk issue, might it?
Issue solved for Fedora 11, too, now: - webkitgtk-1.1.10-1.fc11.x86_64 / midori-0.1.10-1.fc11.x86_64
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.