New shortcut image field is not so visible with Dark theme
Categories
(Firefox :: New Tab Page, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox-esr91 | --- | unaffected |
firefox92 | --- | unaffected |
firefox93 | --- | unaffected |
firefox94 | --- | verified |
firefox95 | --- | verified |
People
(Reporter: atrif, Assigned: secret.okra-0z, Mentored)
References
(Regression)
Details
(Keywords: good-first-bug, regression, Whiteboard: [fidefe-theme], [lang=css])
Attachments
(2 files)
21.54 KB,
image/png
|
Details | |
48 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
|
Details | Review |
Affected versions
- 94.0a1 (20211001093323)
Affected platforms
- Windows 10 x64
- macOS 10.15
- Ubuntu 21.04
Preconditions
- Dark theme
Steps to reproduce
- Open Firefox and a new tab.
- Click on the
Edit this site
option from the Top site's category.
Expected result
- Image field is visible.
Actual result
- Grey background with the Grey image field.
Regression range
- Last good revision: 462b8ab0d119d85c044a1332446b609786fcabc7
First bad revision: 4d1d81ae7b7edc5668d65b6927d907feab8d0e21
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=462b8ab0d119d85c044a1332446b609786fcabc7&tochange=4d1d81ae7b7edc5668d65b6927d907feab8d0e21
Notes
- Attached a screenshot.
Reporter | ||
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 1•3 years ago
|
||
We need a rule in this block targeting the top site tile in the Edit Top Sites modal. It's .top-site-inner > .top-site-button > .tile
. border: 1px solid var(--newtab-border-color)
looks good.
If a contributor works on this, note that you will have to bundle the CSS before you can see your changes. Run ./mach npm run bundle --prefix=browser/components/newtab
. More information here.
Assignee | ||
Comment 2•3 years ago
|
||
Hi everyone, I'm interested in working on this issue.
I'm new to bugzilla would appreciate resources on next steps! Thank you!
Comment 3•3 years ago
|
||
(In reply to secret.okra-0z from comment #2)
Hi everyone, I'm interested in working on this issue.
I'm new to bugzilla would appreciate resources on next steps! Thank you!
Hello and welcome to bugzilla!
You are welcome to work on this issue. We're happy to answer any questions that come up.
In terms of next steps: have you been able to get the Firefox codebase set up on your computer? Some useful information can be found here if not: https://firefox-source-docs.mozilla.org/setup/index.html
Updated•3 years ago
|
Assignee | ||
Comment 4•3 years ago
|
||
I have not — I'll read and work through setup over the weekend!
Thank you for the resource!
Comment 5•3 years ago
|
||
Set release status flags based on info from the regressing bug 1727319
Assignee | ||
Comment 6•3 years ago
|
||
(In reply to Amy Churchwell [:amy] from comment #3)
(In reply to secret.okra-0z from comment #2)
Hi everyone, I'm interested in working on this issue.
I'm new to bugzilla would appreciate resources on next steps! Thank you!Hello and welcome to bugzilla!
You are welcome to work on this issue. We're happy to answer any questions that come up.In terms of next steps: have you been able to get the Firefox codebase set up on your computer? Some useful information can be found here if not: https://firefox-source-docs.mozilla.org/setup/index.html
Hi Amy, I have the codebase set up now! Looking forward to next steps.
Comment 7•3 years ago
|
||
That's great! Harry points out the code block to update in comment 1 along with the command to run to see your CSS changes that affect the new tab page.
I like to combine it with ./mach run
each time I edit something so I don't forget to bundle it:
./mach npm run bundle --prefix=browser/components/newtab && ./mach run
More info about that is in the new tab page docs here.
You can find the quick reference on how to submit a patch here.
Thanks for your help and feel free to ask questions in this bug or on Matrix, if you'd like. The #introduction channel is a welcoming place.
Assignee | ||
Comment 8•3 years ago
|
||
Ok I will do that! Thank you!
Assignee | ||
Comment 9•3 years ago
|
||
Updated•3 years ago
|
Comment 10•3 years ago
|
||
Pushed by htwyford@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6c078da0ec50 Increase visibility of shortcut image field for dark theme. r=harry
Comment 11•3 years ago
|
||
bugherder |
Comment 12•3 years ago
|
||
Please nominate the patch for Beta approval so we can avoid shipping this new regression in Fx94.
Comment 13•3 years ago
|
||
Comment on attachment 9246476 [details]
Bug 1733574 - Increase visibility of shortcut image field for dark theme. r?harry
Beta/Release Uplift Approval Request
- User impact if declined: Low-contrast element in the new tab page.
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): One-line CSS change.
- String changes made/needed:
Comment 14•3 years ago
|
||
Comment on attachment 9246476 [details]
Bug 1733574 - Increase visibility of shortcut image field for dark theme. r?harry
Approved for 94.0rc1.
Comment 15•3 years ago
|
||
bugherder uplift |
Reporter | ||
Comment 16•3 years ago
|
||
Verified fixed with Firefox 95.0a1 (20211024212641) on Windows 10x64, macOS 10.15 and Ubuntu 21.04. The New shortcut image field has a border and can be seen as expected.
Updated•3 years ago
|
Updated•3 years ago
|
Reporter | ||
Comment 17•3 years ago
|
||
Verified fixed with 94.0 (20211025220926) on Windows 10x64, macOS 10.15 and Ubuntu 21.04.
Description
•