Hi Taylor and Raffi,
My apologies as I think I was a bit vague and unclear.
Here's our current process:
- User right clicks in Firefox to share.
- Chrome dialog window is shown where user enters twitter credentials,
message and tags.
- Submit is form posted to server api which includes a number
It would seem that xAuth would be the best method to use as I spent
the last 2 days looking at ways to use oAuth the web way. I'm not if
its entirely possible to do a round-trip in the browser window itself
and pass authorization back to a dialog window that uses XUL.
Why not simply register
The Firefox addon we created works within the native chrome of the
browser. The addon is essentially working within a browser dialog
box, it is limited to its own information so there isn't a way to
redirect the user through the oAuth workflow as there is no place to
return them to. Not much
YCBM,
Is it possible to handle a custom URI scheme in the context of your
extension for the oauth_callback?
Example: You tell the request_token step that your oauth_callback is
supercoolplugin://handle_oauth_callback or something like
chrome://plugin/supercool/handle_oauth_callback (I'm not a
