On Wed, May 19, 2010 at 1:41 PM, Dan Webb <[email protected]> wrote:
> On Wed, May 19, 2010 at 11:27 AM, Steve C <[email protected]> wrote:
>> We just rolled out @anywhere yesterday and some of our users are
>> experiencing similar issues.
>>
>> http://twitpic.com/1p00d6
>
> We rolled out a fix at the weekend that we fixed all the browsers that
> we test under but there are obviously still some browsers getting the
> issue.  I think we'll use console.info to display these message
> instead of an alert.  We wanted to let developers know that they
> needed a clientID in the most noticable way but to avoid unintended
> annoyance of users we'll move to console.log.

Hey Dan,

Just wondering...does TwitPic have a bug or misconfiguration or is
this an @anywhere bug?

Thanks,
-damon

Reply via email to