#9832 closed defect (worksforme)
Browser Back Button changes default action
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ticket system | Version: | 0.11.7 |
Severity: | major | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
When viewing an open ticket and clicking a link there, e.g. to an other ticket referrenced in the description and then using the browser's back button to return to the first ticket, the selection of radio buttons in the "action" area changes from the first option ("leave as new/assigned") to the second ("resolve as [fixed]").
Repeating this (link/back) causes alteration between the first and second options.
In my opinion the severity of the problem is higher than it seems, as in large production systems people tend to enter a comment, look up some referenced ticket, go back and just hit [submit changes], while unintentionally closing the ticket as fixed. In our large company this even caused political problems (as "closed fixed" seemed like an external company frauding the work done).
This behaviour appears in Firefox 3.6 under WinXP, but NOT in IE7 nor in Opera10.
The version of Trac is 0.11.7, as we can't upgrade to 0.12 in production, beacuse our companies hoster won't allow the latest version of python… Therefore I couldn't reproduce the error here at edgewall, as the actions behave a bit different now (e.g. they are folded). The system runs on a SuSE Enterprise Edition 10.3, python 2.4.2
Attachments (0)
Change History (4)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
I just realized that it also happens when I just press F5 to reload the page in Firefox.
I didn't have the opportunity to disable PlugIns yet as this is a productive system under heavy load.
comment:3 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
After installing and updating some PlugIns which didn't really seem to have any connection to this subject, the problem is gone.
I can't really say which of my changes stops the error from appearing (maybe updating the IniAdmin-PlugIn from 0.1 to 0.2 or installing TracCustomFieldAdmin-0.2.5 ?), but I guess as it isn't existing any more I'll close the ticket.
comment:4 by , 14 years ago
Resolution: | fixed → worksforme |
---|
Thanks for the notification!
(fixing resolution)
I just tried to reproduce the problem on the 0.11-Demo (http://trac.edgewall.org/demo-0.11) here which is at 0.11.8dev-r10236 right now, but it didn't happen.
Now testing if it depends on our workflow or any plugin.
I'll report back here if I find anything new.