FUEL/Additions: Difference between revisions
< FUEL
Jump to navigation
Jump to search
Maxauthority (talk | contribs) (→Search) |
(Navigation Events) |
||
Line 58: | Line 58: | ||
== RDF == | == RDF == | ||
Depending on the future status of RDF in the tree, we could use Neil Deakin's [http://www.xulplanet.com/downloads/rdfds/ rdf.js] and a basis for an RDF object. | Depending on the future status of RDF in the tree, we could use Neil Deakin's [http://www.xulplanet.com/downloads/rdfds/ rdf.js] and a basis for an RDF object. | ||
== Navigation Events == | |||
* Document navigation registry | |||
::It seems to be fairly common for extensions to monitor browser navigation events and react to page loads, sometimes only reacting to specific domains or URL Patterns. FUEL could provide a central registry for these types of document navigation listeners to avoid duplication of code and unnecessary overhead. For more details see [[Talk:FUEL/Additions|discussion]]. |
Revision as of 07:30, 18 May 2007
Proposals for additional support in FUEL, of features not addressed yet up to version 0.2
Sidebar
Sidebar interaction.
- load
- toggle
PM (Password Manager)
Handling user logins.
- saveLogin
- removeLogin
- getLoginPwd
- getLogin
Alerts
Anything related to messaging the user.
- Notify (top bar)
- removeNotify
- sysAlert (system alert)
- ... various wrappers around nsIPrompt, including...
- prompt
- confirm
- confirmWithCheck
Search
Search bar utilities
- addEngine
- makeDefault
- switchEngine
Find on page utilities
- find(/foo/, options) will highlight foo on the current web page without opening the find toolbar
- findNext
- findPrevious
Extension
Finding information out about installed extensions
- getList
- getUUID
- getDescription
See: FUEL/0.1/API Extensions / Extension
Request
Wrapper around XMLHttpRequest
Cache
Interaction with the browser cache
Printing utilities
Locale
l10n related
- getLocale
RDF
Depending on the future status of RDF in the tree, we could use Neil Deakin's rdf.js and a basis for an RDF object.
- Document navigation registry
- It seems to be fairly common for extensions to monitor browser navigation events and react to page loads, sometimes only reacting to specific domains or URL Patterns. FUEL could provide a central registry for these types of document navigation listeners to avoid duplication of code and unnecessary overhead. For more details see discussion.