1,273
edits
Labs/Jetpack/Reboot/JEP/102.1: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Dandonkulous (talk | contribs) |
Dandonkulous (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
== JEP 102.1 - Extension | == JEP 102.1 - Extension Auto-Detection == | ||
* Champion: Daniel Buchner - daniel@mozilla.com | * Champion: Daniel Buchner - daniel@mozilla.com | ||
| Line 9: | Line 9: | ||
=== Proposal === | === Proposal === | ||
Enable the extension bar implemented as a result of JEP 102 to | Enable the extension bar implemented as a result of JEP 102 to auto-detect extensions on the web. Through the pairing of a subtle UI notification mechanism and a new extension-specific link tag that sites include on their pages, the browser will signal to users when a site has an extension(s) available on AMO. | ||
=== Open Issues === | === Open Issues === | ||
| Line 17: | Line 17: | ||
* The current test implementation only allows for AMO authorized extensions, should we allow extensions hosted off AMO? | * The current test implementation only allows for AMO authorized extensions, should we allow extensions hosted off AMO? | ||
* Are there user behaviors that we want to watch-out for if we decided to implement this? | * Are there user behaviors that we want to watch-out for if we decided to implement this? | ||
* In my example implementation, I did not account for the person already having an extension that is found on a given website, the extension | * In my example implementation, I did not account for the person already having an extension that is found on a given website, the extension auto-detection mechanism should check the extension IDs that are already installed and skip notification for such extensions. | ||
=== Dependencies & Requirements === | === Dependencies & Requirements === | ||