Slashdot Mirror
Mozilla 1.1 Alpha Released
theBrownfury writes: "Mozilla.org has released Mozilla 1.1 alpha, the first post 1.0 milestone.
This release has been in the works for almost 2 months now incorporating
over 1700 bug fixes and more than a dozen new features. Including: Quartz
rendering for OS X 10.1.5 users, new layout performance enhancements targeted
at DHTML, faster startup times and more. Here are the release notes and
the link to the releases page
or FTP
for downloads."
Hopefully this version will fix the problems I get loading pages with lots of dhtml... takes forever to load those :( (for example, flat mode comments @ shacknews.com)
Anyone know if this has the fix for the remote DoS
when X/XFS is running?
(For those of you who don't know, you can kill X
by including "body { font-size: 1666666px; }" in a stylesheet
My email addy? should be easy enough.
If someone there is worried about people facing this 1.1 new release when, in press releases they have been told about 1.0, then don't worry. The big milestone of 1.0 is about compatibility: the interfaces have been frozen so further development will be easy to do. This is a concert only for enterprises developing applications based on Mozilla technology (PDAs, portable aps, embedded devices), not for the desktop end user.
Singularity: a belief in the "God" idea with the "demiurge" relation inverted.
Now that Quartz rendering is supported, does anyone have experiences in how stable and fast this is compared to Chimera (the Aqua version of Mozilla, not the old X11 browser).
I tried to play pool on yahoo games using sun java but the installation was very clunky. It would just lock up the computer until I installed the Blackdown version of Java.
I took a couple of screenshots of Slashdot rendered with and without the Quartz rendering of Mozilla 1.1A.
Wow. What a difference.
http://www2.canisius.edu/~graciem/mozilla.html
--saint
In traditional /. style I prefer to ask silly questions instead of go googling or reading Bugzilla so here it goes.
Does anyone know if they're planning to replace GTK 1.2 with GTK 2.0 soon as default toolkit on Unix platforms? By default I mean it uses GTK 2.0 if found without having to use --with-toolkit=gtk2 configure option of whatever it's called. I think basic GTK 2.0 support has been in since February or so and I personally tested it sometime in April or May (had to get some patches somewhere and apply to source from CVS, wasn't yet committed back then) and it worked fine on my mainstream system (i686 PC running Debian/unstable). Also some days ago I grabbed some snapshot debs from an APT repository announced on galeon-devel mailing list. Packages included Mozilla with GTK2 support and Galeon compiled from source from the HEAD branch of their CVS. That GNOME 2.0 version of Galeon is already almost quite usable, very cool.
Anyway, IMHO, it would be appropriate to begin public testing of new rendering back-end in early stages of 1.1 alphas by compiling official snapshots for Unices with GTK 2.0 support enabled. Any words regarding the issue?
Kudos on the excellent browser. I couldn't be happier with it... well, maybe a little happier.
I'd love to see a way to allow/block particular plugins for certain websites, as we can now with cookies. A way to globally turn all plugins on/off easily would be useful as well.
OT... the start up speed from 1.0 to 1.1a is significantly faster on my machine, and 1.0 was fast enough for me!
People who prefer Gtk over XUL should probably use Galeon instead of Mozilla.
Yes, I wish they'd add a "disable pipelining for this site" option, as for image loading and such.
I wonder if the developers working on the 1.0.x releases will get bored quickly?
They are the same developers that are working on the 1.x releases. Why would they get bored checking in a fix to the trunk and to the branch?
--Asa
The branch will have a subset of the fixes that land on the trunk. It will not have all of the new features that the trunk has, although some of the features will eventually migrate to the branch after they are well tested on the trunk.
Mozilla builds a set of technologies from which end user products can be built. We provide these technologies to everyone but our primary consumers are companies and organizations that use our technologies in their products. The stable 1.0 branch and the 1.0.x releases on that branch are intended for companies and organizations looking for the most stable technologies they can get. The 1.x development trunk is intended for testing large changes and new features as well as working toward a Mozilla 2.0. We intend to have stable points on the 1.x trunk about once a quarter for those vendors who are a little less conservative or need the latest and greatest feature set for use in their products.
So to answer your question, yes, we will have two different development paths but one will be tracking the other as closely as stability will allow. You won't _have_ to choose from anything but if you're interested in helping us test our latest technologies then please grab trunk (1.x) builds and report any problems. If we need help testing builds on the more conservative 1.0 branch then we'll let you know.
--asa
is awesome. I'm on a 28.8 modem connection for the summer, and I was pretty bummed about how slow webpages were loading up. After turning on the pipelining option, load times dramatically decreased.
There's an explanation on how it works here.
:wq