Closed
Bug 452816
Opened 16 years ago
Closed 14 years ago
Dependency tree does not differentiate visited bugs with a different colour in the Classic style theme
Categories
(Bugzilla :: User Interface, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 365262
People
(Reporter: mossop, Unassigned)
Details
I remember back in the day (yesterday) in the dependency tree a visited link came out purple rather than blue. Seems we have lost this and I miss it.
Updated•16 years ago
|
Summary: Dependency tree does not differentiate visited bugs with a different colour → Dependency tree does not differentiate visited bugs with a different colour in the Classic style theme
Comment 1•16 years ago
|
||
Yeah, if this is true, we should definitely fix it.
Assignee: nobody → ui
Severity: normal → minor
Component: Bugzilla: Other b.m.o Issues → User Interface
Product: mozilla.org → Bugzilla
QA Contact: other-bmo-issues → default-qa
Target Milestone: --- → Bugzilla 3.2
Version: other → 3.2
Comment 2•16 years ago
|
||
Theres a style rule:
.summ A, .summ_deep A {
text-decoration: none;
color: darkblue;
}
so it may be intentional, but that rule has been there since 2006, so....
Comment 3•16 years ago
|
||
(In reply to comment #2)
> so it may be intentional, but that rule has been there since 2006, so....
so this is not a regression. I checked, and Bugzilla 3.0.x also doesn't differentiate visited bugs. Only Bugzilla 2.22.x did.
No longer blocks: bmo-regressions-0808
Keywords: regression
Reporter | ||
Comment 4•16 years ago
|
||
Maybe this was a change in the mozilla.org custom bits? I'm 99% sure that it did this for bmo before the upgrade.
(In reply to comment #4)
> Maybe this was a change in the mozilla.org custom bits? I'm 99% sure that it
> did this for bmo before the upgrade.
As am I, and this has been annoying me quite a bit since then (though not to the degree that I finally chased down this bug until just now ;) ).
Comment 6•15 years ago
|
||
Bugzilla 3.2 is restricted to security bugs only. Moreover, this bug is either assigned to nobody or got no traction for several months now. Rather than retargetting it at each new release, I'm clearing the target milestone and the bug will be retargetted to some sensible release when someone starts fixing this bug for real (Bugzilla 3.8 more likely).
Target Milestone: Bugzilla 3.2 → ---
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•