Hi Ryan. I tried it with the same IE on the bh-demo1.apache.org and it works without a problem! So it must be a problem in 0.5.3 and earlier versions (not sure about 0.6) I've hijacked the following ticket, but will clear it out shortly: https://bh-demo1.apache.org/products/%40/ticket/273#__msie303:comment:15 I also noticed that there is a "# msie303" in the url anchor. Maybe that is related to a fix. Will try the earlier suggested upgrade directly to 0.7 and hopefully the upgrade process itself goes smoothly. On a tangent: what do you guys use for your nightly build automation? Thanks for looking into this! Serge
________________________________ From: Ryan Ollos <[email protected]> To: [email protected]; Serge Bykov <[email protected]> Sent: Tuesday, August 13, 2013 1:02 PM Subject: Re: Bloodhound 0.5.3 IE8 bug On Tue, Aug 13, 2013 at 9:52 AM, Ryan Ollos <[email protected]> wrote: > On Tue, Aug 13, 2013 at 9:02 AM, Serge Bykov <[email protected]> wrote: > >> Hi Devs. >> >> My team has just reported a problem with Bloodhound 0.5.3. When editing >> a description of an existing ticket (ticket modify) using IE 8 >> (8.0.7601.17514) on Windows 7, and clicking 'Submit Changes' button, the UI >> goes back to view mode but nothing is being actually being saved. The >> description remains the original one and no history item added, no email >> goes out. The edit works fine in Chrome and Firefox. >> >> Since anonymous tickets are disabled on the official bloodhound issue >> page, please create a ticket on my behalf and add my email ( >> [email protected]) to the CC for updates. >> >> Thank you kindly! >> Serge > > > Thanks for the report. Reproduced the issue on the nightly build site: > https://bh-demo1.apache.org/ > > It brings to mind other issues that have been seen in the past with IE and > Trac, but some investigation will be needed, > http://trac.edgewall.org/ticket/10382 > I was wrong about that and too hasty too reply. I can't reproduce the issue in IE with either the latest nightly build or the 0.6 release. We are planning to release 0.7 soon, hopefully starting the release process tomorrow. Once 0.7 is released, it would be great if you could upgrade and see if your problem is resolved. In the meantime, could you try reproducing the issue on the nightly build demo site? https://bh-demo1.apache.org/
