Replace autocomplete-profile-listitem-base and the 4 child bindings with Custom Elements
Categories
(Toolkit :: XUL Widgets, task, P5)
Tracking
()
Tracking | Status | |
---|---|---|
firefox67 | --- | fixed |
People
(Reporter: bgrins, Assigned: surkov)
References
Details
Attachments
(1 file, 3 obsolete files)
This is related to (and depends on) Bug 1519486.
There's a set of richlistitems used for form autofill: https://bgrins.github.io/xbl-analysis/tree/#autocomplete-profile-listitem-base.
They share a base class and each specify their own content and methods/properties/constructor etc. These should be able to be converted using the [is] attribute, similar to the process described in Bug 1519486 - probably one CE per XBL binding, but could also consider folding them into a shared class that makes a runtime decision about content.
Should do some manual visual testing using demo pages like: https://luke-chang.github.io/autofill-demo/ as well.
Updated•4 years ago
|
Assignee | ||
Comment 1•4 years ago
|
||
Assignee | ||
Comment 2•4 years ago
|
||
when running dom/base/test/browser_multiple_popups.js the console has
No chrome package registered for chrome://formautofill/content/formautofill.js
uncaught exception: Error opening input stream (invalid filename?): chrome://formautofill/content/formautofill.js
I don't see that formautofill.xml is explicitly included into any of jar.mn files (I guess [2] does the trick), so I didn't do that formautofill.js, but apparently nsChromeRegistry.cpp doesn't like it. Any hints on the issue?
[2] https://searchfox.org/mozilla-central/source/browser/extensions/formautofill/jar.mn#11
Reporter | ||
Comment 3•4 years ago
|
||
(In reply to alexander :surkov (:asurkov) from comment #2)
when running dom/base/test/browser_multiple_popups.js the console has
No chrome package registered for chrome://formautofill/content/formautofill.js
uncaught exception: Error opening input stream (invalid filename?): chrome://formautofill/content/formautofill.js
Is it only that test that has the error, or do you see it when running too?
Assignee | ||
Comment 4•4 years ago
|
||
(In reply to Brian Grinstead [:bgrins] from comment #3)
(In reply to alexander :surkov (:asurkov) from comment #2)
when running dom/base/test/browser_multiple_popups.js the console has
No chrome package registered for chrome://formautofill/content/formautofill.js
uncaught exception: Error opening input stream (invalid filename?): chrome://formautofill/content/formautofill.jsIs it only that test that has the error, or do you see it when running too?
Browser Toolbox's console has no such errors, when running the browser
Comment 5•4 years ago
|
||
See https://phabricator.services.mozilla.com/D17945#459017
This code is in a system add-on so should be self-contained.
Reporter | ||
Comment 6•4 years ago
|
||
Assignee | ||
Comment 7•4 years ago
|
||
Updated•4 years ago
|
Assignee | ||
Comment 8•4 years ago
|
||
Updated•4 years ago
|
Assignee | ||
Comment 9•4 years ago
|
||
Reporter | ||
Updated•4 years ago
|
Updated•4 years ago
|
Comment 10•4 years ago
|
||
Pushed by surkov.alexander@gmail.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/d09c7dc93f20 convert formautofill autocomplete-profile-listitem bindings to CE, r=MattN
Comment 11•4 years ago
|
||
bugherder |
Updated•4 years ago
|
Description
•