I know this is off-topic but I need to rant against Google/Blogger's mobile version of their platform since I keep running into it whenever I'm browsing HN on my iPhone.
When I view this article on an iPhone 4S, Blogger adds in a swipe feature that goes to the next article (or previous article if you swipe left).
This "feature" is driving me nuts because there are tables that break the screen on the iPhone where I cannot move around to view it because Blogger automatically assumes I want to read the next article.
If someone from Google is reading this, or even better Blogger. Please take this feature out. It is a really annoying experience.
If you want to create a cross-browser extension, you can use an API such as Kynetx, Webmynd, CrossRider, or KangoExtensions. Links and pros/cons can be found here: http://stackoverflow.com/questions/4913123/cross-browser-ext...
Last time I looked it was a maze trying to figure out FF extensions. A painful long learning curve. I wrote my first chrome/safari extension about 5 mins after I read the intro.
Speaking of Opera, there's a labs release out that supports extensions on Opera Mobile: http://dev.opera.com/articles/view/extensions-opera-mobile-l...
I love how they don't even mention IE!
Chrome, Opera and Safari have a very similar extension architecture. If very easy to port on extension to the other 2 borwsers, as long as: * the API is there. For example only chrome can block HTTP requests, and access headers. * The UI element is there. Safari has no page action, for example
This is really just about writing a browser extension that injects code into a page and does nothing else. Firefox extensions can do all sorts of things (modify the browser UI, call functions in system libraries, create protocol handlers, perform raw IO) that other environments don't permit.
Many of these things probably can't be done through Jetpack/Add-on SDK, but, for better or for worse, Firefox's extension mechanism is vastly more powerful than that of Chrome or Opera.