Closed
Bug 1517476
Opened 6 years ago
Closed 5 years ago
[meta] Investigate moving some functions from browser.js into the new address bar code once QuantumBar rewrite is complete
Categories
(Firefox :: Address Bar, task, P3)
Firefox
Address Bar
Tracking
()
RESOLVED
DUPLICATE
of bug 1610472
People
(Reporter: standard8, Unassigned)
Details
(Keywords: meta)
User Story
- losslessDecodeURI could move to UrlbarUtils, as it is window independent. -- https://searchfox.org/mozilla-central/rev/0ee0b63732d35d16ba22d5a1120622e2e8d58c29/browser/base/content/browser.js#2669 - URLBarSetURI could move to UrlbarInput. -- https://searchfox.org/mozilla-central/rev/0ee0b63732d35d16ba22d5a1120622e2e8d58c29/browser/base/content/browser.js#2621 -- isInitialPage should move with it -- checkEmptyPageOrigin / SetPageProxyState may be able to move, but needs some investigation.
There's a few functions that I think we should investigate moving into the new QuantumBar code once the new code is enabled by default.
Some of these are still used in the existing urlbarBindings, so I don't think we should move them before we're ready to remove that.
See the user story for details of the functions - I'm using that, so we can add more to this list as we spot them.
Updated•6 years ago
|
Priority: -- → P3
Updated•6 years ago
|
Updated•6 years ago
|
Summary: Investigate moving some functions from browser.js into the new address bar code once QuantumBar rewrite is complete → [meta] Investigate moving some functions from browser.js into the new address bar code once QuantumBar rewrite is complete
Updated•6 years ago
|
Blocks: 1551227
No longer depends on: quantumbar
Updated•6 years ago
|
Type: enhancement → task
Updated•5 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•