ntim also removed the feed binding by building DOM using JS instead.Tim Nguyen (ntim) removed unused functions from textbox and then simplified it to rely on instead.Students from the Canberra Grammar School school stopped by the Mozilla office and made their first contributions to Firefox by removing the menulist-description and menu-vertical bindings.Paolo continued his panel simplification work by removing the panelmultiview binding. Paolo Amadini removed the autocomplete-result-popup, autocomplete-base-popup, autocomplete-tree, autocomplete-treebody, autocomplete-treerows bindings.Neil Deakin removed the unused menubutton-item binding.Dão also removed the tabbrowser binding, after I converted the implementation into a JS class (above).Dão Gottwald removed the windowdragbox binding by initializing the WindowDraggingUtils on the titlebar in browser.js instead.There are 215 more bindings left, compared to 240 from the last update and 300 from the start of the project. I’m hoping this same approach can apply to other large bindings, like. Thanks to the reviewers in that bug for sticking with it, and to Potch for upgrading his xmlom package to include XML comments. Our largest binding (tabbrowser) was translated into a JS class using the converter script plus manual fixups. It turned out that the separate search bar in the toolbar was the only instance that still depended on the intricacies of the version, and once that was fixed we could convert all the other autocomplete popups to use the version, and remove the bindings that implemented a customized for this use case. The older implementation was based on the element, and in the past few years we’ve been replacing more and more of its uses with the new implementation based on the element, to overcome the styling and layout limitations of. We used to have two separate implementations of the “autocomplete” popup, which is used for combo boxes and for text input fields with an attached drop-down. Also, we were able to delete the XBL accessibility platform integration and eliminate a few more bindings that were only used to attach roles to elements. This is a big milestone since we will now be able to migrate any binding to a Custom Element and maintain accessibility. This work can be seen in Bug 1428930 and blockers. We moved all of the remaining attributes out of XBL and into the accessibility platform code. The easiest way to follow along with this work is to watch the main meta bug. Since the last update we’ve continued to remove bindings and have been making progress on accessibility, autocomplete widgets, and migrating XBL to JS. This is the fourth edition of the XBL Replacement Newsletter.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |