Currently XBLBinding contains all sort of attributes and methods that should be distributed into dedicated classes so that we can share some objects between bindings. Patch forthcoming.
Created attachment 22949 [details] Add 2 new classes and distribute XBLBinding content among them
Created attachment 22978 [details] Better changes: uses the boundDocument instead of the boundElement, restore some code changed by mistake
I've been slow, but I'll look at this patch later today.
Is prototype a name that the spec uses. If not, I would prefer we used another name as to not conflate the term with its usage in JS.
(sorry for the delay) (In reply to comment #4) > Is prototype a name that the spec uses. If not, I would prefer we used another > name as to not conflate the term with its usage in JS. prototype is not defined in the specification but derives from the design pattern used. I agree with changing it: I propose XBLBindingElementInfo to match XBLDocumentInfo.
David Hyatt, could you have a look at this patch? It should bring XBL closer to the structure Mozilla currently use.
Comment on attachment 22978 [details] Better changes: uses the boundDocument instead of the boundElement, restore some code changed by mistake r=me for xbl branch.
Committed in r37603.