We just rolled out @anywhere yesterday and some of our users are
experiencing similar issues.
http://twitpic.com/1p00d6
Steve
On May 14, 6:57 pm, Larry la...@topsy.com wrote:
I just came across a coworker's browser that triggered analert() call
fromanywhere.js. While okay for development, the
On Wed, May 19, 2010 at 11:27 AM, Steve C st...@twitpic.com 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
What is your ETA on rolling out the change? We are deciding on whether
we should disable @anywhere until alert() is removed.
On May 19, 2:41 pm, Dan Webb d...@twitter.com wrote:
On Wed, May 19, 2010 at 11:27 AM, Steve C st...@twitpic.com wrote:
We just rolled out @anywhere yesterday and some
On Wed, May 19, 2010 at 1:41 PM, Dan Webb d...@twitter.com wrote:
On Wed, May 19, 2010 at 11:27 AM, Steve C st...@twitpic.com 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
On Wed, May 19, 2010 at 11:48 AM, Damon Clinkscales sca...@pobox.com wrote:
On Wed, May 19, 2010 at 1:41 PM, Dan Webb d...@twitter.com wrote:
On Wed, May 19, 2010 at 11:27 AM, Steve C st...@twitpic.com wrote:
Just wondering...does TwitPic have a bug or misconfiguration or is
this an @anywhere
Thanks Dan- We appreciate you your teams hard work.
On May 19, 2:53 pm, Dan Webb d...@twitter.com wrote:
On Wed, May 19, 2010 at 11:48 AM, Damon Clinkscales sca...@pobox.com wrote:
On Wed, May 19, 2010 at 1:41 PM, Dan Webb d...@twitter.com wrote:
On Wed, May 19, 2010 at 11:27 AM, Steve C
One of us is crazy here. If I'm not wrong console.log belongs to
firebug. Which means you will get a javascript error on ALL browsers
which do not have firebug installed and running.
-Nischal
On May 19, 11:41 pm, Dan Webb d...@twitter.com wrote:
On Wed, May 19, 2010 at 11:27 AM, Steve C
I am assuming they will create a dummy function that will be used
console.log is undefined- otherwise, you are very right.
On May 19, 3:03 pm, nischalshetty nischalshett...@gmail.com wrote:
One of us is crazy here. If I'm not wrong console.log belongs to
firebug. Which means you will get a
I think throw() seems more appropriate. Firebug and WebKit-based
browsers will work with console.log(). A javascript error for an
undefined function would still be better than an alert().
Larry
On May 19, 12:03 pm, nischalshetty nischalshett...@gmail.com wrote:
One of us is crazy here. If I'm
Phew... I would have agreed if u guys had said I was crazy too... I
follow these threads to understand and learn new stuff... :)
-Nischal
On May 20, 12:07 am, Steve C st...@twitpic.com wrote:
I am assuming they will create a dummy function that will be used
console.log is undefined- otherwise,
Any update on this? I'm getting it on a site for certain users/
browsers even though it's all configured correctly as well.
The alerts are very intrusive for a production website when things are
configured correctly. Especially with user emails rolling in
complaining about getting the error.
Are we really talking about incorrect installations here? Twitter's
own @Anywhere documentation page (http://dev.twitter.com/anywhere/
begin) is throwing this same error in older browsers, including Chrome
3.0.195.
On May 15, 6:26 pm, Abraham Williams 4bra...@gmail.com wrote:
I agree that
This does sound like a regression of some kind. We'll get this fixed ASAP.
On Sat, May 15, 2010 at 3:41 PM, JohnB johnfakor...@yahoo.com wrote:
Are we really talking about incorrect installations here? Twitter's
own @Anywhere documentation page (http://dev.twitter.com/anywhere/
begin) is
Our site has been running @anywhere for over a week now without error.
Yesterday my coworker was getting the alert(). He is running an older
version of Firefox (3.0.8) on Ubuntu, so there might be another cause
other than missing clientID or version?
I still believe alert() is intrusive,
I can reliably reproduce this with Firefox 3.0.8 at the following url:
http://cornsyrup.org/~larry/anywhere/index.html
Error console is reporting S.get is not a function
Larry
On May 15, 11:31 am, Larry la...@topsy.com wrote:
Our site has been running @anywhere for over a week now without
I agree that @Anywhere should degrade gracefully when configured properly on
unsupported platforms and not prompt incorrect alert()s. But I do think
alert()s are probably the best way to notify developers of incorrect
installations.
Abraham
On Sat, May 15, 2010 at 11:55, Larry la...@topsy.com
Firefox 3.X is a supported browser for @anywhere and my example is
properly configured, yet it triggered when it wasn't supposed to. This
highlights my point of why alert() not a good choice for notification
of incorrect installations. Instead maybe it should use throw(). That
would be more useful
Isn't console.log() specific to firebug? #JustSaying :)
On May 16, 4:43 am, Larry la...@topsy.com wrote:
Firefox 3.X is a supported browser for @anywhere and my example is
properly configured, yet it triggered when it wasn't supposed to. This
highlights my point of why alert() not a good
Chrome has it too.
On Sun, May 16, 2010 at 03:20, nischalshetty nischalshett...@gmail.comwrote:
Isn't console.log() specific to firebug? #JustSaying :)
On May 16, 4:43 am, Larry la...@topsy.com wrote:
Firefox 3.X is a supported browser for @anywhere and my example is
properly configured,
19 matches
Mail list logo
