Closed
Bug 453070
Opened 16 years ago
Closed 11 years ago
noscript: nonsensical status/resolution combination shown for open bugs
Categories
(Bugzilla :: Creating/Changing Bugs, defect, P5)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: tuukka.tolvanen, Unassigned)
References
(Depends on 1 open bug)
Details
On loading an bug in NEW state on bmo without js enabled, it appears as [NEW v] resolved as [FIXED v] duplicate of [ ] The 'duplicate of' part I can live with, but the FIXED part is pretty bad degradation :( One way to deal with this would be to combine the status and resolution selects into one at least for open bugs (bug 452954); another would be to have a blankish resolved as [--- v] item available in the resolution dropdown, which would probably be removed by js for the script-enabled user. Being able to manipulate the status and resolution selects into disallowed combinations when script is not enabled is one thing that's perhaps in the realm of acceptable for noscripted users, but the current state being expressed as a disallowed combination is signifigantly more wrong :|
Updated•16 years ago
|
Severity: normal → minor
Priority: -- → P4
Updated•16 years ago
|
Priority: P4 → P5
Comment 2•11 years ago
|
||
Users with JS disabled must accept to have a lower user experience than users with JS enabled. Scenarios with JS disabled are not something we consider anymore. Wontfix.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•