I tried this in FF3.1Bb2 and I couldn't post from that version either.
Twitter update that broke it maybe then?
Very possible. I wish firebug was working here.
Summary: update button on twitter no longer works (after 2008-12-19 tracemonkey merge) → update button on twitter no longer works (after 2008-12-19 tracemonkey merge?)
The fancy scripty version is trying to send updates to s.twitter.com which is NXDOMAIN everywhere I've tried to resolve it, so it definitely looks like a twitter issue.
Just confirmed that the "update" button no longer works on Firefox 3.1 Beta 2 nor Beta 1, so my suspicion of this being due to the most recent tracemonkey merge seems imprudent. The update button *does* still work in Firefox 3.0.x, though. I'm adding some more people and moving to Core::General since it's not clear to me that this isn't potentially due to some of the new content restriction stuff we've been working on since early betas. It would be nice to get a regression window, in terms of at what point between Firefox 3 and 3.1 builds this stops working so we know where to look.
Assignee: general → nobody
QA Contact: general → general
Summary: update button on twitter no longer works (after 2008-12-19 tracemonkey merge?) → update button on twitter no longer works (since 2008-12-19, affecting as far back as beta 1)
Duplicate of this bug: 470643
Flags: blocking1.9.1? → blocking1.9.1+
from Ryan Flint: http://getsatisfaction.com/twitter/topics/why_wont_twitter_let_me_post_new_updates_anymore http://getsatisfaction.com/twitter/topics/opera_suddenly_doesnt_work Looks like this might just be a twitter.com issue, though I don't know why it is that I can get Firefox 3 to work reliably.
This regressed between 20080930050845 - http://hg.mozilla.org/mozilla-central/rev/86b982e8b73e and 20081001 - http://hg.mozilla.org/mozilla-central/rev/63b0791327ab
Within that range are: - tracemonkey merge - xmlhttprequest access control work both of which feel like potential good places to start. Though, Ryan's links and comment 5 indicate it could be some combination thereof plus a bad reaction to the s.twitter.com bit.
Ryan: How is twitter trying to send data to s.twitter.com? Using XHR, <script src="http://s.twitter.com/..."> or something else? The only thing that the Access-Control patches *should* have affected is if a script tries to do XHR.open("cross domain URI"). Such a command used to throw, but now doesn't. It's seems unlikely that twitter would be relying on that, although it is of course possible.
Ugh, not much we can do other than evangelize then :(
Assignee: nobody → english-us
Component: General → English US
Product: Core → Tech Evangelism
QA Contact: general → english-us
Target Milestone: mozilla1.9.1b3 → ---
Version: 1.9.1 Branch → unspecified
--> Tech Evangelism: usual suspects, do we have any contacts at Twitter? Ryan: got a URL/reference to the ticket you filed?
Assignee: english-us → arabic
Component: English US → Arabic
QA Contact: english-us → arabic
Assignee: arabic → english-us
Component: Arabic → English US
QA Contact: arabic → english-us
I have one - let me see what I can do.
I mailed Alex Payne @ Twitter. He works on backend stuff, but probably knows someone on the front end team. Hoping that he's reading work mail today.
can I suggest to also message @twitter directly on twitter ?
Duh, yeah, thanks Daniel. I'll do that.
(In reply to comment #15) > Ryan: got a URL/reference to the ticket you filed? #348414 filed Saturday evening. I just poked it again to see if I can get someone to respond. Cooked up http://twitter.com/rflint/status/1071766890 as an easy workaround in the meantime.
They're now aware: http://status.twitter.com/post/66263547/unable-to-post
Seems like it's fixed now.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Yay!! Thanks guys, that rocks!
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.