Closed
Bug 2012519
Opened 4 months ago
Closed 4 months ago
Replace usage of `newtab-toast-dismiss-button` with a new set of strings
Categories
(Firefox :: New Tab Page, task)
Firefox
New Tab Page
Tracking
()
RESOLVED
FIXED
149 Branch
| Tracking | Status | |
|---|---|---|
| firefox149 | --- | fixed |
People
(Reporter: mconley, Assigned: dgrant)
References
Details
Attachments
(1 file)
I see that the newtab-toast-dismiss-button string is used here: https://searchfox.org/firefox-main/rev/69888f58354c8d44e854945761a9e8fa954512d1/browser/extensions/newtab/content-src/components/DiscoveryStreamComponents/PersonalizedCard/PersonalizedCard.jsx#39
However, that string was removed in bug 1998975. We need to either replace this string with it's label and aria-label. It might be worth making its identifier more generic for the various messages we're likely to display inline on newtab, rather than it being toast-centric.
| Reporter | ||
Updated•4 months ago
|
Summary: Remove usage of `newtab-toast-dismiss-button` → Replace usage of `newtab-toast-dismiss-button` with a new set of strings
Updated•4 months ago
|
Assignee: nobody → dgrant
Updated•4 months ago
|
Attachment #9542150 -
Attachment description: Bug 2012519 - Replace usage of newtab-toast-dismiss-button → WIP: Bug 2012519 - Replace usage of newtab-toast-dismiss-button
Updated•4 months ago
|
Attachment #9542150 -
Attachment description: WIP: Bug 2012519 - Replace usage of newtab-toast-dismiss-button → Bug 2012519 - Replace usage of newtab-toast-dismiss-button
Pushed by dgrant@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/b31cd1b1bce9
https://hg.mozilla.org/integration/autoland/rev/d581d53bfb2e
Replace usage of newtab-toast-dismiss-button r=home-newtab-reviewers,reemhamz,fluent-reviewers,bolsson
Comment 4•4 months ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 4 months ago
status-firefox149:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 149 Branch
Updated•3 months ago
|
QA Whiteboard: [qa-triage-done-c150/b149]
You need to log in
before you can comment on or make changes to this bug.
Description
•