#6985 closed defect (fixed)
Field permissions do not work for drop-downs
Reported by: | Owned by: | Russ Tyndall | |
---|---|---|---|
Priority: | normal | Component: | TimingAndEstimationPlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 0.11 |
Description
The ticket permisssions that can be set in the [field settings] section of a trac.ini file do not work with Drop-Down (<select>) fields. This is because your stream modifiers only target <input> fields.
Attachments (0)
Change History (7)
comment:1 Changed 15 years ago by
comment:2 Changed 15 years ago by
comment:3 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
I think the above change should fix it for you, please upgrade to the latest version (0.9.2)
Feel free to reopen, if this didnt adequately address your needs.
HTH, Russ
comment:4 Changed 15 years ago by
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Heya
That did what we needed it to do, but a similar one just cropped up - disabling a <select> field appears to hide it, instead of displaying the contents. (Again, this would appear to be because the code specifically targets <input> fields, but I don't know enough about Python or the Blackmagic plugin to troubleshoot it.)
- Josh
comment:5 Changed 15 years ago by
I think I see what you mean. I will try to get to this pretty soon
comment:6 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
comment:7 Changed 15 years ago by
Thanks so much for the continued feedback. So often I never hear back about changes I make. I made a second stab at solving this issue. I addressed it more directly this time and just special cased the select since it operates fundamentally differently than inputs (options and what not).
I tested both disabled and hide and both seemed to do basically what I expected, hopefully they will for you as well.
Please let me know (reopen) if you have further issues,
Russ
Thanks for the report, expect a bug fix this week