Password import suggestion renders without text (MigrationUtils.getBrowserName is not a function)
Categories
(Toolkit :: Password Manager, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox-esr78 | --- | unaffected |
firefox77 | --- | unaffected |
firefox78 | --- | unaffected |
firefox79 | + | wontfix |
firefox80 | + | fixed |
People
(Reporter: Mardak, Assigned: Mardak)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(2 files, 1 obsolete file)
Bug 1618311 is currently experimenting in 77 and 78 and bug 1518234 removed getBrowserName
in 79, so if the experiment is successful and decide to turn things on, we'll definitely want to fix this as it also prevents future password popups from rendering too.
Comment 1•5 years ago
|
||
Is there a separate bug on file about adding automated tests for this feature?
Assignee | ||
Comment 2•5 years ago
|
||
There's various bugs that have been filed and deferred until the experiment concludes blocking bug 1617759. Looks like there isn't even one yet to turn things on by default where we probably want to rework some bits of how the experiment was implemented as well as adding tests.
For fixing this, looks like we'll want to do something similar for the imported bookmarks folder "From Google Chrome" behavior:
https://searchfox.org/mozilla-central/rev/a87a1c3b543475276e6d57a7a80cb02f3e42b6ed/browser/components/migration/MigrationUtils.jsm#649-654
Comment 3•5 years ago
|
||
(In reply to Ed Lee :Mardak from comment #2)
There's various bugs that have been filed and deferred until the experiment concludes blocking bug 1617759. Looks like there isn't even one yet to turn things on by default where we probably want to rework some bits of how the experiment was implemented as well as adding tests.
For fixing this, looks like we'll want to do something similar for the imported bookmarks folder "From Google Chrome" behavior:
https://searchfox.org/mozilla-central/rev/a87a1c3b543475276e6d57a7a80cb02f3e42b6ed/browser/components/migration/MigrationUtils.jsm#649-654
The problem is that the autocomplete code isn't async, and we can only really get these strings async. I have an alternative patch.
Comment 4•5 years ago
|
||
This also switches to using individual strings for each browser.
This is very repetitive, but it has a few advantages:
- no need for a second, asynchronous localization pass in the code, which likely
wouldn't work well for autocomplete code - it's always clear for localizers what browser names are available
- localizers can do proper grammar around the names of browsers as would be
appropriate in their language. - there's no dependency on strings in browser/ from code in toolkit
(though obviously there's still a dependency on the actual migration code..)
Comment 5•5 years ago
|
||
Set release status flags based on info from the regressing bug 1518234
Updated•5 years ago
|
Comment 6•5 years ago
|
||
Per discussion with Ed, he wants to try to get a patch that does not require any string changes.
Updated•5 years ago
|
Assignee | ||
Comment 7•5 years ago
|
||
Narrowly fix the regression without string changes by hardcoding english strings for the browsers used in the experiment.
Updated•5 years ago
|
Comment 8•5 years ago
|
||
Changing the priority to p1 as the bug is tracked by a release manager for the current beta.
See What Do You Triage for more information
Comment 10•5 years ago
|
||
bugherder |
Comment 11•5 years ago
|
||
The patch landed in nightly and beta is affected.
:Mardak, is this bug important enough to require an uplift?
If not please set status_beta
to wontfix
.
For more information, please visit auto_nag documentation.
Updated•5 years ago
|
Description
•