Mozilla 1.2 Beta Released

nberardi writes "Mozilla 1.2 Beta is out. Typeahead now works on Mac and Java now works on Jaguar. On Linux, the classic theme now picks up GTK native theme. See the release notes for more info."

Comments

Link prefetching

[Rhubarb Crumble]

check this out: Link prefetching

seems to mean that if you're reading page 1 of a multi-page article, page 2 will be loaded in the background. nice!

Re:Link prefetching

[Rhubarb Crumble]

And if your reading a page with links you dont want to click, lets say to a picture of a man stretching his balloon knot open, then they'll be cached for you and swallow up more and more system resources. nice!

That's a fair point - there is potential for abusem since the web page decides which "hints" to issue. Hopefully it'll eventually have an "enable prefetching for these sites"-type access control, similarly to the way it's done with cookies. Or a limit on the amount of data to prefetch.

Re:Link prefetching

[Eimi Metamorphoumai]

How is this worse than just embedding the image into the webpage, possibly with height=0 width=0? When you go to a webpage you already pretty much give it carte blanche to download what it likes; this doesn't seem very different.

Re:Link prefetching

[Ed Avis]

The style of web browsing I use is to load all the links I want to read in new windows by clicking on them with the middle button. Then they can be loading in the background while I read the first part of the article. It forms a kind of queue of pages to read, so when I've finished reading the first page I just close that window and go on to the next (which is ready instantly). The result is up to a hundred browser windows open at once - but I know that I'm not the only person who browses like this. Of course, it helps to have a browser which can open lots of windows without thrashing and slowing the machine to a crawl (like Dillo) or one that has tabbed browsing.

This style of following links can also work well with offline browsing and a proxy server designed for offline use like WWWOFFLE. If you go online briefly and click on all the links you want to load, the proxy remembers to download them. Then a few minutes later you can go online again and all the pages will be loaded ASAP. Once they've loaded you can disconnect again and continue browsing. This makes the most sense for people whose internet access is metered (hmm, I wonder if something like this could work for palmtops).

But what I'd really like to see in a browser is an explicit 'to read' queue. When you click on a link with the middle button, it doesn't immediately open in a new window or tab but instead is added to the queue and starts downloading in the background. On the browser's toolbar there is a 'next page' button which goes to the next URL you have marked for reading.

Automatic prefetching of all links from a page, la wget -r, would be crazy for many heavily-linked sites. But you could have heuristics for it or specify particular sites where the link following should be more aggressive.

Type ahead find is great

[fault0]

Type ahead find is great. Been using it since Moz 1.2 alpha. The neat thing is that you can type a search phrase, and you can search again with ctrl-G. My only suggestion would be to have type ahead and find searches appear in a history combobox in the find window.

Moz versus IE

[0x0d0a]

With the two rapid releases of Phoenix and Mozilla, with Netscape (the browser) being pushed by AOL, and with Chimera popular on the Mac, IE may have more users, but aside from being more stable and configurable, Moz is now steadily heading for a 1-1 user:browser ratio. Hopefully, this will result in an extremely customized browsing experience.

Re:If only...

[evbergen]

Sadly, there isn't even any such thing as OS native widgets on Unix. Every toolkit has its own, and every application gets to choose its own toolkit.

We need an X protocol that works at widget level instead of pixel level. It'd be great if we could design /that/, together with a good widget definition language, and to stop reinventing the OS in huge toolkits that even provide timers and I/O and mistreat X as a dumb framebuffer backend.

Client-side rendering, high-level application frameworks, *yuck*. Provide your high-level GUI stuff through an IPC channel and get out of the way. Let me have my own main loop back. Thank you.

Mozilla's feature flood

[Jugalator]

I really have to say that I find the recent development of Mozilla very inspiring as it brings completely new, unique features to the users. First came integrated popup and advertisement blocking. A simple but effective feature. Then came Type Ahead. Then came link prefetching. Now, in what time span?

I don't know about you, but at least my opinion is that the browser software has suffered from some serious stagnation during the past years. Since Internet Explorer 4.0 and its CSS and "DHTML" (mostly Javascript+CSS) support, I haven't seen much development in the browsers at all. Opera was innovative with mouse gestures, but I think the browser that truly turns this stagnation of browser features that's often limited to things like "slightly better CSS support", etc is Mozilla. I'm not even sure how it's possible for the team to bring so many new features in such a short time. Is it a side effect from being open source with browser enthusiasts working on it day and night? Is it "just" because a very flexible and well written code base? An efficient organization of the mozilla developers? A combination?

IMHO, the changes in Mozilla from a late version such as 1.0 are surely larger (at least more useful) than the changes since Internet Explorer 4.0. Each new version is right now bringing lots of new features. Perhaps that will change in the future, but I'll enjoy it while it lasts for sure. :-)