Closed
Bug 1497687
Opened 6 years ago
Closed 6 years ago
Use fluent for Update History in Update section of Preferences
Categories
(Firefox :: Settings UI, defect, P3)
Firefox
Settings UI
Tracking
()
RESOLVED
DUPLICATE
of bug 1497694
People
(Reporter: songqing, Unassigned)
References
Details
Attachments
(1 obsolete file)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36
Steps to reproduce:
This bug converts of searchkeywords attributes of Show Update History button in Update section of Preferences (https://searchfox.org/mozilla-central/source/toolkit/mozapps/update/content/history.xul) to using Fluent for localization.
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Comment 1•6 years ago
|
||
Reporter | ||
Updated•6 years ago
|
Summary: Use fluent for Show Update History button in Update section of Preferences → Use fluent for Update History in Update section of Preferences
Reporter | ||
Comment 2•6 years ago
|
||
(In reply to Qinghao Song from comment #0)
> User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6)
> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36
>
> Steps to reproduce:
>
> This bug converts the Update History in Update section of Preferences, as well as the searchkeywords attribute of Show
> Update History button (https://searchfox.org/mozilla-central/source/toolkit/mozapps/update/content/
> history.xul) to using Fluent for localization.
Reporter | ||
Comment 3•6 years ago
|
||
This bug converts the Update History in Update section of Preferences, as well as the searchkeywords attribute of Show
Update History button (https://searchfox.org/mozilla-central/source/toolkit/mozapps/update/content/history.xul) to using Fluent for localization.
Reporter | ||
Updated•6 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
Reporter | ||
Updated•6 years ago
|
Resolution: INVALID → DUPLICATE
Updated•6 years ago
|
Attachment #9015699 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•