There are three different possible <select>s in template/en/default/flag/list.html.tmpl that can be used for flags. All but one has a check that makes the <select> disabled if the user can't request it. Not sure why that one was missed, but it should be fixed.
I see no reason to mark it as disabled, even if you cannot change it. The reason this one is not disabled is because this flag already exists while in the other two cases, the flag doesn't exist yet. In the case described in this bug, the user would see a flag with a single option, which is the one already selected. I'm fine with that.
Change the other two <select>s instead rather than modifying the first one incorrectly.
Comment on attachment 321092 [details] [diff] [review] patch - v2 Tested on both 3.0.4 and 3.1.4. r=LpSolit
Attachment #321092 - Flags: review?(LpSolit) → review+
Severity: normal → minor
Target Milestone: --- → Bugzilla 3.0
tip: Checking in template/en/default/flag/list.html.tmpl; /cvsroot/mozilla/webtools/bugzilla/template/en/default/flag/list.html.tmpl,v <-- list.html.tmpl new revision: 1.32; previous revision: 1.31 done BUGZILLA-3_0-BRANCH: Checking in template/en/default/flag/list.html.tmpl; /cvsroot/mozilla/webtools/bugzilla/template/en/default/flag/list.html.tmpl,v <-- list.html.tmpl new revision: 220.127.116.11; previous revision: 18.104.22.168 done
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.