Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

[Bug] Can't read text on about screen when in private mode #7414

Closed
sblatz opened this issue Dec 30, 2019 · 11 comments
Closed

[Bug] Can't read text on about screen when in private mode #7414

sblatz opened this issue Dec 30, 2019 · 11 comments
Labels
🐞 bug Crashes, Something isn't working, .. eng:qa:verified QA Verified eng:ready Ready for engineering Feature:PrivateBrowsing Feature:Settings good first issue Good for newcomers help wanted Help wanted from a contributor. More complex than good first issue. P2 Upcoming release S2 Major Functionality/product severely impaired and a satisfactory workaround doesn't exist
Milestone

Comments

@sblatz
Copy link
Contributor

sblatz commented Dec 30, 2019

If you go to the "About Fenix" page in private mode, the text cannot be read. We're probably just using the wrong attribute color here.

image

┆Issue is synchronized with this Jira Task

@sblatz sblatz added 🐞 bug Crashes, Something isn't working, .. good first issue Good for newcomers help wanted Help wanted from a contributor. More complex than good first issue. labels Dec 30, 2019
@boek boek added Feature:Themes Dark mode, light mode, private browsing mode Feature:Settings P2 Upcoming release S2 Major Functionality/product severely impaired and a satisfactory workaround doesn't exist labels Dec 30, 2019
@sblatz sblatz added Feature:PrivateBrowsing and removed Feature:Themes Dark mode, light mode, private browsing mode labels Dec 30, 2019
@obitodarky
Copy link

@boek I would like to work on this Issue. Can you help me out with a few things?

@boek
Copy link
Contributor

boek commented Dec 31, 2019

Yes, for sure!

How can I help?

@obitodarky
Copy link

I would like to know which build variant should I work on and where can I find the file which mentions the text color.

@KaairaGupta
Copy link
Contributor

@boek I have worked a bit on this issue, and i needed some help with it. Is there a difference between how the private mode theme works in dark and light modes? If so, then where in the code can i find it because this problem persists just in the light mode

@ekager ekager added the eng:ready Ready for engineering label Jan 8, 2020
@KaairaGupta
Copy link
Contributor

@boek i have fixed the bug and am making a PR. Are there any guidelines that i have to follow for the same? It's my first time with open source

@KaairaGupta
Copy link
Contributor

@boek @ekager please review my PR

@ekager
Copy link
Contributor

ekager commented Jan 8, 2020

Reopening for QA

@ekager ekager reopened this Jan 8, 2020
@KaairaGupta
Copy link
Contributor

@ekager can you please let me know why this issue is reopened? Was there any mistake in my PR, and how should i proceed if there was?

@ekager
Copy link
Contributor

ekager commented Jan 9, 2020

No issue! Our process is just to keep issues open until our QA team can verify that they've been fixed.
In the future, you can use the keyword "For #7414" instead of "Closes #7414" to help me out :)

@ghost
Copy link

ghost commented Jan 9, 2020

@ekager The shared documentation states that:

An example commit message summary looks like, Closes #5: Upgrade gradle to v1.3.0.".

Yet, most commits to this repository (as well as other Mozilla repositories) mainly use the For or Fixes keywords instead. Also, I can't find a reference to the For keyword anywhere. Do we just use For when we don't want to automatically close the linked issue and Closes when we do?

@AndiAJ
Copy link
Collaborator

AndiAJ commented Jan 10, 2020

Hi, verified as fixed on the latest Nightly Build #20100616 from 01/10 using the following devices:
• Google Pixel 3a (Android 9)
• Huawei Mate 20 Lite (Android 8.1.0)
• Samsung Galaxy S7 (Android 7)
• OnePlus A3 (Android 6.0.1)
• LG Nexus 4 (Android 5.1.1)

► Screenshot
rsz_screenshot_20200110-085717

@AndiAJ AndiAJ closed this as completed Jan 10, 2020
@AndiAJ AndiAJ added eng:qa:verified QA Verified and removed eng:qa:needed QA Needed labels Jan 10, 2020
@liuche liuche mentioned this issue Jan 22, 2020
32 tasks
@liuche liuche added this to the v3.2 milestone Jan 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🐞 bug Crashes, Something isn't working, .. eng:qa:verified QA Verified eng:ready Ready for engineering Feature:PrivateBrowsing Feature:Settings good first issue Good for newcomers help wanted Help wanted from a contributor. More complex than good first issue. P2 Upcoming release S2 Major Functionality/product severely impaired and a satisfactory workaround doesn't exist
Projects
None yet
Development

No branches or pull requests

7 participants