MozillaSecurity / MozillaSecurity/FuzzManager

Style the "ID" links with a visited-link color, in fuzzing crash/results tables, so that you can tell which entries you've looked at.

Open
#802 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
208
Forks
48
Avg merge
23h 5m
Merged PRs (30d)
2

Description

STR:
(1) Visit https://fuzzmanager.fuzzing.mozilla.org/crashmanager/crashes/
(2) Click an entry in the first column (ID)
(3) Navigate back

EXPECTED RESULTS:
The link that you clicked should be a different color.

ACTUAL RESULTS:
The link is the same color as all the others.

This seems to be because we're styling them with

// Links
a {
  color: @link-color;
  text-decoration: none;

...in scaffolding.less, and we're not providing a different color in a :visited rule.

(Note, @link-color seems to be a LESS variable, which ends up as color: #337ab7; in the actual CSS. I'm not sure where it's defined, and I don't know LESS particularly well. But presumably this section of scaffolding.less is where we would want to define a :visited style for these links, and we'd want to define the color in the same spot where @link-color is defined.)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the behavior at the crash manager crashes page by opening an ID link and navigating back. Inspect scaffolding.less and locate the definition of @link-color, then verify that the crash/results table ID links show a distinct visited color while preserving the existing link styling.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
frontend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.