Mozilla pushes out second Firefox 3.1 alpha Mozilla has released the second alpha of Firefox 3.1 a week after Google unveiled its shiny new browser, Chrome. The latest advance version of the Mozilla Foundation’s upcoming browser is codenamed “Shiretoko”, and is intended for trailblazing software developers and testers only. Meanwhile, the so-called “code freeze”, or …
>No you can't. You can only drag URLs to existing tabs. The original tab stays there, and you don't create a new tab where you drop it either.
Umm, no, he's right, you can drag tabs to other instances, I've been doing it for months. Firefox 3.0x - open two copies of Firefox, open 2 tabs in each one (for clarity, make sure all 4 tabs are different sites). Drag a tab from Firefox(1) into Firefox(2), and the net result is Firefox(1) has 1 tab, and Firefox(2) has 3 tabs.
However, *you have to drop the tab onto the tab bar* Dropping the tab onto the browser page causes the behaviour you describe
Mine's the coat with the middle of the fence in the pocket.
Do you mean to imply that a journalist made a statement without trying to verify his facts?
Recall the recent journalistic furor around the release of Google's "new" browser, notable only for its inability to block Google's ads.
I could point a finger at journalists and make faces and shout rude names. However, it's not like this is a new phenomenon. Frankly, I'm probably an even bigger fool for constantly being disappointed.
>Do you mean to imply that a journalist made a statement without trying to verify his facts?
I would never dare to suggest that ;-) Maybe it was just a quick skim of the press releases?
>Actually, it's *one* instance with two windows.
Very true. Is that how Chrome handles it too? They claim one tab = one thread which would be nice, especially if it's one container app, like Firefox
Shame I can't try it (no windows box at home, work blocked install)
Well, let's hope that they make that crappy new URL bar optional, fix the postscript printing on Solaris/Linux, and get the performance back to snuff, else I'm staying on FF2.
I didn't realise how slow FF3 was until I went back to FF2 because of the first two problems, and boy did FF seem fast :(
Straw poll, how many non-developers know or more importantly care to install a different browser to IE.... I'd argue not that many. How many non-developers are going to visit w3schools.... I'd argue not that many...
"Anyway, our data, collected from W3Schools' log-files, over a five year period, clearly shows the long and medium-term trends"
Go to a football match at Wembley, between say ManU and Chelsea, and carry out a straw poll of people outside the grounds who their favourite team is. 45% ManU, 45% Chelsea, 10% other. Now ask the whole country, and get a much more different, and more RELEVANT statistic...
Statistics are dangerous, because people use them to misrepresent facts.
Chrome is actually one *process* per tab, plus a process for the tab manager, plus a process for add-ins.
It gives all the isolation that a process offers but it's a huge overhead when browsing many tabs - especially cos a lot of tabs will just contain an image/attachment/simple html page.
I would have liked to see something like the .NET AppDomain model but I'm not sure of how cross-platform that would be....
Maybe I'm missing the ball here, but according to http://www.infoworld.com/archives/emailPrint.jsp?R=printThis&A=/article/08/08/22/Mozilla-boosts-JavaScript-performance_1.html, the 3.1 trunk was supposed to include native code compilation for JS. Running 3.1 alpha is just as slow on SunSpider tests as 3.0.
Ho hum, uninstall Shiretoko for me then!
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2023
