Why is it safer Tom?
Safer for who? Cheers, Dean ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Tom van der Woerdt Sent: Saturday, April 30, 2011 12:09 PM To: [email protected] Subject: Re: [twitter-dev] New oAuth Authorization screen is unusable on phone webbrowser control I've heard this before. It sounds like all UIWebView, WebBrowser and probably Android's WebView are blocked. This is definitely a good thing for security reasons. The "workaround" I recommend: launch the actual browser, using a <yourapp>:// link (something like myapplication://tokenDone) as the return URL. This is a LOT safer for the users. Tom On 4/30/11 8:50 AM, Bob12345 wrote: Hi, I've been using a WebBrowser control in my Window Phone application to login into Twitter. Today I noticed that the login/authorization page format had changed and it is now unusable in a web browser control that my application displays. The text on the page is squeezed together, and the page unscrollable. If I paste the URI into the desktop browser it displays a full-sized desktop login screen listing all of the app's capabilities. Is anybody else having this issue? Do you know of a workaround for this problem? Thanks! -Bob -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
