Link decoration makes it impossible to see accesskeys

NEW
Unassigned

Status

()

Bugzilla
User Interface
--
minor
15 years ago
4 years ago

People

(Reporter: Luke Reeves, Unassigned)

Tracking

(Blocks: 1 bug)

Details

(Whiteboard: [wanted-bmo], URL)

Attachments

(1 attachment)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030327 Debian/1.3-4
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030327 Debian/1.3-4

In the show_bug.cgi component, there are access keys specified for the input
controls.  The problem is that an underline tag is used to markup the access key
- and this underline is invisible because of the already-underlined link.

Changing the link style, perhaps to no underlining, would fix this.

Reproducible: Always

Steps to Reproduce:
(Reporter)

Updated

15 years ago
Keywords: access
access keyword is used for Mozilla-related bugs, not for Bugzilla.

confirming since I can't find any dupes.  Zippy's QA reported this also.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: access
Target Milestone: --- → Bugzilla 2.18
Version: unspecified → 2.17.3
Severity: normal → minor
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
(Reporter)

Updated

14 years ago

Comment 2

13 years ago
This bug has not been touched by its owner in over six months, even though it is
targeted to 2.20, for which the freeze is 10 days away. Unsetting the target
milestone, on the assumption that nobody is actually working on it or has any
plans to soon.

If you are the owner, and you plan to work on the bug, please give it a real
target milestone. If you are the owner, and you do *not* plan to work on it,
please reassign it to nobody@bugzilla.org or a .bugs component owner. If you are
*anybody*, and you get this comment, and *you* plan to work on the bug, please
reassign it to yourself if you have the ability.
Target Milestone: Bugzilla 2.20 → ---

Updated

12 years ago
QA Contact: mattyt-bugzilla → default-qa

Updated

11 years ago
Assignee: myk → ui

Updated

11 years ago
Blocks: 345674
Created attachment 519440 [details] [diff] [review]
remove anchor decoration

simple fix; remove underlining from links, only show underline on hover.

this makes the ui look a lot cleaner; currently we have a mix of underlined and non-underlined links on the same page.
Assignee: ui → glob
Status: NEW → ASSIGNED
Attachment #519440 - Flags: review?(guy.pyrzak)
Target Milestone: --- → Bugzilla 4.2
Whiteboard: [wanted-bmo]

Comment 4

7 years ago
Comment on attachment 519440 [details] [diff] [review]
remove anchor decoration

Review of attachment 519440 [details] [diff] [review]:

I'm find for doing this for the labels, but doing it for the whole UI is bad. Colorblind users rely on underlining for a visual que that other links are clickable (http://www.useit.com/alertbox/20040510.html). The change in this causes ALL links to not have underlines without any other visual queue other than the blue. I'd prefer to see this change limited to just the labels.
Attachment #519440 - Flags: review?(guy.pyrzak) → review-

Comment 5

7 years ago
Comment on attachment 519440 [details] [diff] [review]
remove anchor decoration

needs full reviewer
Attachment #519440 - Flags: review?(mkanat)

Comment 6

7 years ago
Comment on attachment 519440 [details] [diff] [review]
remove anchor decoration

nm, I r- this one.
Attachment #519440 - Flags: review?(mkanat)

Updated

7 years ago
Target Milestone: Bugzilla 4.2 → Bugzilla 5.0

Comment 7

5 years ago
We are going to branch for Bugzilla 4.4 next week and this bug is either too invasive to be accepted for 4.4 at this point or shows no recent activity. The target milestone is reset and will be set again *only* when a patch is attached and approved.

I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else.
Target Milestone: Bugzilla 4.4 → ---
Assignee: glob → ui

Updated

4 years ago
Status: ASSIGNED → NEW
You need to log in before you can comment on or make changes to this bug.