Open Bug 1841773 Opened 1 year ago Updated 3 months ago

The link displayed after extension migration appears gray instead of blue as in Figma

Categories

(Firefox :: Migration, defect, P3)

Desktop
All
defect

Tracking

()

Tracking Status
firefox-esr102 --- unaffected
firefox-esr115 --- unaffected
firefox115 --- unaffected
firefox116 --- affected
firefox117 --- affected

People

(Reporter: atrif, Unassigned, Mentored)

References

(Blocks 3 open bugs)

Details

(Keywords: good-first-bug, Whiteboard: [lang=css])

Attachments

(2 files)

Attached image image.png

Found in

  • 116.0b1

Affected versions

  • 116.0b1
  • 117.0a1 (2023-07-04)

Preconditions

  • random extensions installed on Chrome
  • browser.migrate.chrome.extensions.enabled:true

Tested platforms

  • Affected platforms: Windows 10x64, macOS 12, Ubuntu 22.04
  • Unaffected platforms: none

Steps to reproduce

  1. Open the new migration window and import extensions.
  2. Observe the Extensions link.

Expected result

  • The Extensions link is blue per Figma

Actual result

  • The Extensions link is grey.

Regression range

  • Not a regression.

Additional notes

  • Attached a screenshot.
  • This happens for all three scenarios (full success, partial success, no matches).

:atrif, if you think that's a regression, could you try to find a regression range using for example mozregression?

Priority: -- → P3

To help Mozilla out with this bug, here's the steps:

  1. Comment here on the bug that you want to volunteer to help.
    This will tell others that you're working on the next steps.
  2. Download and build the Firefox source code
    • If you have any problems, please ask on Element/Matrix in the #introduction channel. They're there to help you get started.
  3. Start working on this bug.
    • If you have any problems with this bug, please comment on this bug and set the needinfo flag for me. Also, you can find me and my teammates on the #fx-desktop-dev channel on Element/Matrix most hours of most days.
  4. Build your change with mach build and test your change by importing extensions from Chrome. Also check your changes for adherence to our style guidelines by using mach lint.
  5. Submit the patch (including an automated test, if applicable) for review. Mark me as a reviewer so I'll get an email to come look at your code.
  6. After a series of reviews and changes to your patch, I'll push it to autoland.
Mentor: tgiles
Keywords: good-first-bug
Whiteboard: [lang=css]

Hi, I am looking into this bug and interested to work on it

Hi Tim, I would like to work on this, can you let me know if I can submit a patch or is someone else working on this.
Also could you let me know if there are any test cases that needs to written.

Assignee: nobody → nithinkumar4200
Status: NEW → ASSIGNED
Attachment #9345253 - Attachment description: Bug 1841773 - Added css class to fix the anchors in the extensions section. r?tgiles → Bug 1841773 -Revision of Added css class to fix the anchors in the extensions section. r?tgiles
Attachment #9345253 - Attachment description: Bug 1841773 -Revision of Added css class to fix the anchors in the extensions section. r?tgiles → Bug 1841773 - Use LinkText for link color in migration wizard in the extensions section. r?tgiles

This good-first-bug hasn't had any activity for 2 months, it is automatically unassigned.
For more information, please visit BugBot documentation.

Assignee: nithinkumar4200 → nobody
Status: ASSIGNED → NEW
No longer blocks: 1838427
Depends on: 1838427
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: