Prev: Which roulette strategy can win at online roulette or prove that Albert Einstein was wrong
Next: FAQ Topic - Why do some posts have <FAQENTRY> in them? (2010-07-13)
From: Garrett Smith on 12 Jul 2010 17:51 Twitter.com website uses a login URI that is inaccessible; the user cannot log in using the form UI. Attempting to log in to twitter.com in Firefox, for example, the browser displays the error to the user | Server not found | Firefox can't find the server at staging45.local.twitter.com. | * Check the address for typing errors such as | ww.example.com instead of | www.example.com | | * If you are unable to load any pages, check your computer's network | connection. | | * If your computer or network is protected by a firewall or proxy, | make sure that Firefox is permitted to access the Web. It's not a Firefox issue; it's that Twitter.com's login FORM's action references a URI that cannot be accessed (staging45.local.twitter.com). To login to twitter via web, go to http://twitter.com and change the form's action, either using Firebug or with this bookmarklet: javascript:void(document.getElementById("signin").action = "/sessions"); There's been a host of other problems, including broken back button, as well as some bad approaches used in the javascript. -- Garrett
From: David Mark on 12 Jul 2010 20:00 On Jul 12, 5:51 pm, Garrett Smith <dhtmlkitc...(a)gmail.com> wrote: > Twitter.com website uses a login URI that is inaccessible; the user > cannot log in using the form UI. Attempting to log in to twitter.com in > Firefox, for example, the browser displays the error to the user > > | Server not found > | Firefox can't find the server at staging45.local.twitter.com. > | * Check the address for typing errors such as > | ww.example.com instead of > | www.example.com > | > | * If you are unable to load any pages, check your computer's network > | connection. > | > | * If your computer or network is protected by a firewall or proxy, > | make sure that Firefox is permitted to access the Web. > > It's not a Firefox issue; it's that Twitter.com's login FORM's action > references a URI that cannot be accessed (staging45.local.twitter.com). > > To login to twitter via web, go tohttp://twitter.comand change the > form's action, either using Firebug or with this bookmarklet: > > javascript:void(document.getElementById("signin").action = "/sessions"); > > There's been a host of other problems, including broken back button, as > well as some bad approaches used in the javascript. > -- Yes, that site is some piece of work. Their biggest mistake was hiring jQuery Ninjas to write the front-end. If investors could comprehend the ramifications of such decisions, there'd be far less major disasters out there.
From: Garrett Smith on 13 Jul 2010 01:52
On 2010-07-12 05:00 PM, David Mark wrote: > On Jul 12, 5:51 pm, Garrett Smith<dhtmlkitc...(a)gmail.com> wrote: >> Twitter.com website uses a login URI that is inaccessible; the user >> cannot log in using the form UI. Attempting to log in to twitter.com in >> Firefox, for example, the browser displays the error to the user >> >> | Server not found >> | Firefox can't find the server at staging45.local.twitter.com. >> | * Check the address for typing errors such as >> | ww.example.com instead of >> | www.example.com >> | >> | * If you are unable to load any pages, check your computer's network >> | connection. >> | >> | * If your computer or network is protected by a firewall or proxy, >> | make sure that Firefox is permitted to access the Web. >> >> It's not a Firefox issue; it's that Twitter.com's login FORM's action >> references a URI that cannot be accessed (staging45.local.twitter.com). >> >> To login to twitter via web, go tohttp://twitter.comand change the ......................................^ There was a space character (U+0020) there. >> form's action, either using Firebug or with this bookmarklet: >> >> javascript:void(document.getElementById("signin").action = "/sessions"); >> >> There's been a host of other problems, including broken back button, as >> well as some bad approaches used in the javascript. >> -- > And there, though it, as well as the previous two characters which remain, should have been removed by the responder. -- Garrett |