Hi Kevin,

This is a feature on the teams roadmap. We don't have a timeline for when or
if this will be implemented but we know it's something developers would like
to see. If anything does happen it will be communicated either through
@twitterapi or this mailing list.

Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris


On Fri, Jan 7, 2011 at 3:40 PM, KevinB <[email protected]> wrote:

> Thanks for the official Tweet Button - it's nice to have something
> familiar and consistent for our users.
>
> Our current implementation is to have a Tweet button on a mobile
> website. Functionally it works great, but the Share Box (and login, if
> necessary) don't work very well on a mobile device (iPhone, in
> particular - I haven't tested in Android). The fixed width:
>
> http://dev.twitter.com/pages/tweet_button_faq#dimensions
>
> helps a little bit, but the form fields and labels are still quite
> small since the device zooms out the page to fit everything in it.
> This requires the user to zoom in to be able to see exactly what's
> going on. And if I don't use the actual button and just open
> twitter.com/share with a querystring, it's even worse b/c of the
> iPhone's assumption that web pages are 960px wide.
>
> My request is that the HTML/CSS of the Share Box login and post be
> updated with CSS media queries (or a separate page) to accommodate the
> smaller screen.
>
> thanks!
> -KevinB
>
> --
> 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

Reply via email to