New Twitter has a login popup everytime I open it. I am already logged in. I can close this popup and my twitter experience is not effected. Why is this thing even there?
Is the popup a HTTP Basic Auth window? If so, are you using Firefox? This is a ridiculously elusive bug that a couple of us have been trying to diagnose. It appears to be buried in the FF implementation of XHR when a reference to an XHR instance is shared across iFrames. We're working on it.
New Twitter Has Become Browser Poison
101–108 of 108 posts
Re: New Twitter Has Become Browser Poison
#102New Twitter has a login popup everytime I open it. I am already logged in. I can close this popup and my twitter experience is not effected. Why is this thing even there?
Is the popup a HTTP Basic Auth window? If so, are you using Firefox? This is a ridiculously elusive bug that a couple of us have been trying to diagnose. It appears to be buried in the FF implementation of XHR when a reference to an XHR instance is shared across iFrames. We're working on it.
Re: New Twitter Has Become Browser Poison
#103Earlier quoted context omitted.
Yes, they do...and then they want it to do the Snazzy New Thing that didn't even exist when the thing was built (and integrate with the Wonderful Service and the other Hot Newness). These are the two omnipresent and conflicting goals that people want out of any computer that's even vaguely general-purpose. Wait long enough, and you'll see it happen on iPads, too. ETA: I mean, Hell, we're talking about a page in a web…
Yes, and I do sympathize. This stuff isn't like a light switch that you turn on and have the room all lit up despite whatever changes have been made to the backend with the transmission lines and generators, etc. But sometimes we want it to act that way.
Re: New Twitter Has Become Browser Poison
#104Re: New Twitter Has Become Browser Poison
#105Re: New Twitter Has Become Browser Poison
#106Re: New Twitter Has Become Browser Poison
#107Earlier quoted context omitted.
Me too. The overhead is slightly higher, but having crashes and memory leaks confined to a single tab is awesome.
They're not confined to a single tab for me. It seems like child tabs go in the parent process, for example, so I usually get 2-5 tabs crashing at once. I also get more crashes with Chrome than I used to get with Firefox, but maybe I'm just opening more tabs.