Closed
Bug 1774156
Opened 2 years ago
Closed 2 years ago
[Experiment] The “browsing” string from the “Start browsing” button starts with uppercase instead of lowercase
Categories
(Firefox :: Messaging System, defect, P1)
Firefox
Messaging System
Tracking
()
VERIFIED
FIXED
Iteration:
103.2 - June 13 - June 24
Tracking | Status | |
---|---|---|
firefox101 | --- | unaffected |
firefox102 | --- | verified |
firefox103 | --- | unaffected |
People
(Reporter: srosu, Assigned: emcminn)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
30.54 KB,
image/png
|
Details |
[Affected versions]:
- Firefox Beta 102.0b7 (Build ID: 20220612185901)
[Affected Platforms]:
- Windows 10 x64
- macOS 12.3.1
- Linux Mint 20.2
[Prerequisites]:
- Have the Firefox Release browser, en-US locale installed.
- Have a new Firefox profile created.
- Have the “nimbus.debug” pref set to true.
- Have the “browser.search.region” pref set to “US”.
[Steps to reproduce]:
- Open the Firefox browser with the profile from prerequisites.
- Navigate to the ‘about:studies?optin_slug=about-welcome-mobile-download&optin_branch=treatment-a&optin_collection=nimbus-preview’ URL.
- Restart the browser.
- Navigate to the “about:welcome” page.
- Dismiss all the slides by clicking the “Not now” button until the “Get Firefox on your phone” slide is displayed.
- Observe the button’s label.
[Expected result]:
- The “browsing” string starts with lowercase.
[Actual result]:
- The “browsing” string starts with uppercase.
[Additional notes]:
- This issue is reproducible in both Treatment branches of the experiment.
- Based on Figma, the ”browsing” string should start with lowercase.
- Attached is a screenshot of the issue.
Assignee | ||
Updated•2 years ago
|
Assignee: nobody → emcminn
Comment 1•2 years ago
|
||
Looks like the messages were updated to use mr2-onboarding-start-browsing-button-label = Start browsing
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Updated•2 years ago
|
Iteration: --- → 103.2 - June 13 - June 24
Priority: -- → P1
Updated•2 years ago
|
Blocks: ms-deployments
Updated•2 years ago
|
Comment 2•2 years ago
|
||
This issue was part of the work done on the QA-1521 request which was signed-off as GREEN. Considering this I am marking this issue as Verified.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•