Closed
Bug 1823643
Opened 2 years ago
Closed 2 years ago
In ProviderQuickSuggest::blockResult, check result.payload.isBlockable instead of re-determining whether blocking is enabled
Categories
(Firefox :: Address Bar, task)
Firefox
Address Bar
Tracking
()
RESOLVED
FIXED
113 Branch
Tracking | Status | |
---|---|---|
firefox113 | --- | fixed |
People
(Reporter: dao, Assigned: dao)
References
(Blocks 1 open bug)
Details
(Whiteboard: [snt-urlbar-result-menu])
Attachments
(1 file)
Following up from bug 1823608. It doesn't seem to make sense to re-determine whether blocking is enabled when that same information is already available via result.payload.isBlockable
.
Updated•2 years ago
|
See Also: → https://mozilla-hub.atlassian.net/browse/SNT-577
Assignee | ||
Updated•2 years ago
|
Summary: Check result.payload.isBlockable in ProviderQuickSuggest::blockResult instead of re-determining whether blocking is enabled → In ProviderQuickSuggest::blockResult, check result.payload.isBlockable instead of re-determining whether blocking is enabled
Assignee | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
Assignee: nobody → dao+bmo
Status: NEW → ASSIGNED
Pushed by dgottwald@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/4abc4e55049e
In ProviderQuickSuggest::blockResult, check result.payload.isBlockable instead of re-determining whether blocking is enabled. r=adw
Comment 3•2 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox113:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 113 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•