287
edits
XUL:Element APIs: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 4: | Line 4: | ||
There should be more consistency of attributes, properties etc. Basically a comprehensive review and uplift. For example, some elements have an icon property called "image", others "src", some both. | There should be more consistency of attributes, properties etc. Basically a comprehensive review and uplift. For example, some elements have an icon property called "image", others "src", some both. | ||
'''Comprehensive Review of Public vs. Private''' | |||
Non-public methods, properties and fields should be prefixed with m or _. When JS2 comes, these should be genuinely private. | |||
'''Some Stuff Shouldn't Be In Toolkit''' | |||
Firefox regularly makes changes to the tabbrowser. It's of little real interest to other apps. There are also some not-necessary other items in there that potentially require many months of review and uplift. Some items should move into browser, some items should move into a real toplevel mozapps directory so that the uplift work on the "supported" toolkit is simpler. | |||
'''Counter-Intuitive Binding Attachment''' | '''Counter-Intuitive Binding Attachment''' | ||
| Line 15: | Line 23: | ||
...but it seldom works out that well. If an item has no frames constructed, attachment doesn't occur until it is inserted into the document. | ...but it seldom works out that well. If an item has no frames constructed, attachment doesn't occur until it is inserted into the document. | ||
'''allowevent and mousethrough''' | |||
The [[XUL:AllowEvents|allowevent and mousethrough]] attributes are a bit confusing. | |||