Opened 18 years ago
Closed 18 years ago
#920 closed bug (fixed)
Trac erroneously set the action to something else with each reload
Reported by: | axeld | Owned by: | johndrinkwater |
---|---|---|---|
Priority: | normal | Milestone: | Website R1 |
Component: | Website/Trac | Version: | R1/pre-alpha1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
Open a bug, hit reload, and the action will be changed - every time you reload, it will jump one option further. Pretty annoying when you change something else, and all of a sudden, you resolved or accepted a bug.
Attachments (2)
Change History (9)
comment:1 by , 18 years ago
Cc: | added |
---|
comment:2 by , 18 years ago
Milestone: | Haiku R1 → Website R1 |
---|
comment:3 by , 18 years ago
Just had a very quick look: could be the browser doesn't (but should) reset variables between reloads, a potential fix is posted below. Excuse me for not testing it; can not with the current Trac permissions.
by , 18 years ago
Attachment: | Haiku-from-rev1j-live.patch added |
---|
comment:4 by , 18 years ago
Cc: | removed |
---|---|
Owner: | changed from | to
Unfortunately, this didn't fix it. I've added you to the developers group. Hopefully that helps.
comment:6 by , 18 years ago
Status: | new → assigned |
---|
Figured this bug out: It only affects Mozilla & Firefox users :( Opera + Konq don't show signs of the bug. I didn't really believe it, but after lots of DOM digging, I had a good search of Bugzilla for any syptoms of this. To name a few, bugs 270071, 254129, 311507, and 175289.
Because of how componentselect works (it removes + adds components to the page) it enters one of those edge cases where the GRE doesn't do too well. I'll look into mooting the problem, if it can be done with a js hack :)
For a little testcase, try here: http://www.quirksmode.org/js/tests/moz_radios.html
(ticket intentionally accepted)
by , 18 years ago
Attachment: | Broken-mozilla.patch added |
---|
Work-around (eugh) for Mozilla problem; apply to a clean rev1j
comment:7 by , 18 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Thanks for the patch. I hope Mozilla gets to fixing those bugs, finally.
This seems to be a bug in our componentselect code. It must be somewhere in updateSelection(). John, could you please have a look?