Slashdot Mirror
Gran Paradiso Alpha 3
kbrosnan writes "Gran Paradiso Alpha 3 is a release of the Gecko rendering engine for testing purposes only. Here are the release notes. While this release uses the interface of Firefox, no significant interface changes have been made. These alpha releases focus on making improvements to the core elements: graphics, JavaScript, page rendering, etc."
* Animated PNG (APNG) images are now supported.
* The DOM clientLeft and clientTop attributes are now supported.
* Introduced support for , which puts resources into the browser's offline cache. This allows a web application to ensure that its resources are available in the cache when the browser goes into offline mode. See * * * Marking Resources for Offline Use for further details on offline support.
* Improved precision of layout and scaling across a wide range of screen and printer resolutions.
* Implemented cycle collection in XPCOM, which detects cases where two released objects hold one another, but neither is held by anyone else. In this scenario, both objects can safely be purged. Previously, the holds each has on the other would have prevented them from being purged.
* Added support for the HttpOnly cookie attribute, which marks a cookie as readable only by the server and not by client-side scripts.
* Added a new preference, "Warn me when web sites try to redirect or reload the page", which notifies the user when the page specifies HTTP-EQUIV=refresh.
* Windows 95, Windows NT 4, Windows 98, and Windows ME are not supported for Gecko 1.9.
* OS X 10.2 is no longer supported, and OS X 10.3.9 or better is required.
* The non-standard JavaScript Script object is no longer supported.
* Moving DOM nodes between documents now requires a call to importNode or adoptNode as per the DOM specification.
It's kind of sketchy that they're not supporting older Windows or OS X versions, but I don't think that's a huge deal. I wish they'd reintroduced MNG instead of APNG (purely a personal preference; APNG is probably actually a better way of doing it), and any fixes to JavaScript are nice to have.
"You can either have software quality or you can have pointer arithmetic, but you cannot have both at the same time."
I thought it was a GTA mod....
It's an alpha release of Firefox 3, it uses the Gecko 1.9 engine.
Yes, it does completely pass the Acid 2 CSS compliance test.
Slay a dragon... over lunch!
I consider it a feature if a browser prevents people from visiting MySpace.
"At a certain point, this sort of decision has to be made: Move forward, or live in the past. The technical issues that surround supporting old systems verses moving forward with more elegant solutions for modern systems."
I dub thee Vista.
WTF? Where did the cars go?
I do not think it means what you think it means.
Which I suppose makes your post ironic. Hmm.
On OSX, Gran Paradiso Alpha 3 had an annoying habit of flashing a white screen before redrawing a page. To test this, just go to http://www.mozilla.org/products/ and click from tab to tab.
One can only hope that this won't occur in the release versions, because it is really quite annoying.
Apart from dropping support for older OS's, is this really worthy of being /.'d?
It's an alpha of the Gecko engine. The most interesting features are APNG and some enhancement for offline browsing. Seriously, what the hell? This isn't Digg...
Don't worry...he's just been hanging out with Alanis Morsette. On second thought, worry.
I was looking at the mozilla wiki and I couldn't find a release schedule for Gecko 1.9 / Firefox 3. Does it exist somewhere? I read allusion to like March and then to the end of the year. I guess if we are still in Alpha, its more like Q3/Q4 ?
I tried recent nightly builds, and I really liked what I saw on the painting front. I hope we can get a stabilized release soon.
If they "fixed" this "leak", the other bunch of fucknozzles would come back asking "Why are back and forward so slow?!??". I think for the time being you people are slightly less annoying, so the "leak" stays.
Is this the first browser that supports APNG?
Is there a way to run both firefox and Paradiso without affeting firefox settings and extensions etc ?
TechSutra
I think he actually meant redundant.
What i want its an updated windows gecko component (activex better than .net) with his own native api not a ie cloned one (http://www.iol.ie/~locka/mozilla/control.htm) if Xul Runner based much better
Having the app (firefox) its nice... but a component would be better. I must use crappy ie-control for work because there is not an updated gecko component
I work hacking internal apps for a medical research company in borland delphi, scheme and dolphin smalltalk. Like me, many people arent good enought at c or have the time to hack something out of firefox.
I had a feeling the rendering engine improvements would break something. The Quick Contacts list of GMail with Chat has a huge space on the bottom that increases each time you hover over a user. I wonder if it's a rendering engine bug or a GMail bug.
Want a high quality FOSS RTS game? Try Warzone 2100!
It's possible to turn off the back-forward cache by setting browser.sessionhistory.max_viewers to 0 in about:config. That said, for some users, Firefox uses a lot of memory due to actual leaks rather than this kind of caching.
The shareholder is always right.
For OSX users, Gran Paradiso is a huge improvement over previous Firefox versions. It's way faster, and it feels as fast as Safari. While there are still some bugs especially with forms, this is definitely something OSX users should try.
{{.sig}}
A browser consuming hundreds of megs of ram is hardly a reasonable trade-off for a slightly faster back button that people rarely use to begin with.
Fucknozzles! That's a new one. I suppose if you've already got an asshat, you need some matching fucknozzles to go with it.
There's only single "Linux" download link that refers to Linux/x86 binary. If leading Free Software project doesn't treat non-x86 platforms seriously, how can we expect something different from e.g. hardware manufacturers?
I wish fucknozzles would stop claiming the leak was from the back-forward caching, when it leaks like a sieve even with that feature turned off.
Still just text zoom I see. Not a full page zoom option yet. I thought I read it would be in alpha3?
this really does mean that we'll have Mac-native widgets now as another poster said, and perhaps they'll throw in color management so that I can consider replacing Safari with Firefox. A lot of people criticize Safari, but its rendering engine actually appears to be superior--it passes the Acid2 test for instance.
Is it just me?
I tried to use Firefox and Camino on OSX, but I found very many sites displaying with tiny text. The font appeared way smaller than it should and was very difficult to read. Yes, I know I could set a minimum font size but I'd have to do it for every font, and it would mess up pages where there was a good reason for a tiny font.
Safari rendered all of the pages fine, so now I just use safari, but it did make me wonder. Doesn't anyone else have this problem with Gecko based browsers?
j'ai découvert une démonstration vraiment admirable (de ce théorème général) que cette si
If you don't have write-access to c:\beta\firefox, then you are not the administrator. If you are not the administrator of a machine, and the administrator refuses to grant you this write access, then you probably shouldn't be running alpha software on the machine.
Other browsers have shown (Opera, Safari) that it's possible to have speedy back and forward buttons without taking up a gig of memory. You can claim that the Firefox back-forward code is so poorly written that it would have to be redone from the ground up, and that the developers consider a new spellchecker to be higher-priority than a time-consuming rewrite of this memory-hogging component. But please don't pretend that this is an intrinsic trade-off in browser design.
Ceci n'est pas une sig
browser.cache.memory.enable
That's pretty crappy programmer logic, though.
Because we have more available, we should feel free to waste more?!
Memory usage is essentially constant. The fractional delay of the history button is... what... fifteen seconds combined out of a dozen hours of browsing?
It's not programmer logic. The "fastback" feature was one of the most requested enhancements before it was added. It was at the request of users that the feature was added, not because of "crappy programmer logic." Anyway, the feature seems to use only tens of megabytes at most (at least on the vast majority of web sites), and can be turned off entirely if it's using too much memory for your liking.
What a fool believes, he sees, no wise man has the power to reason away.
Nice rant, but Firefox does not seem to use more memory than other browsers. See my above posts and the following links:
Radically New IE 7 or Updated Mozilla Firefox 2--Which Browser Is Better?
IE 7 vs IE 6
Firefox 2 - the lean, mean browser
If you can give a set of steps that causes Firefox to use "up to a gig of memory" and does not cause other browsers to use nearly as much memory, let's have it. Then whatever problem you're seeing can be reported and fixed.
What a fool believes, he sees, no wise man has the power to reason away.
Ironically, it's exactly this sense of the word that most people are claiming Alanis failed at. For example, neither "Rain on your wedding day" or "A traffic jam when you're already late" are outside of what might naturally be expected -- as many people have observed, it's simply bad luck. One could argue that both qualify as an outcome "as if in mockery of the promise and fitness of things", but the problem with this is that they don't meet the test of being opposite to what might naturally be expected. One could further argue that these outcomes might not be what was expected, but having unrealistic expectations thwarted by everyday reality is not ironic.
Other questionable examples of Alanis-irony include "Good advice that you just didn't take" and "a black fly in your Chardonnay". The best explanation I've heard is that by writing a song about irony which used examples which were not ironic, Alanis was indulging in meta-irony. Who knew she was such an intellectual?!
I'm sorry, but "someday ram will be cheap as hell, so who cares!" is the definition of crappy programmer logic. And that's what the poster prior had just commented on. Just because drives are 500gb doesn't mean you should't optimize your application to use as little as possible.
Anyway, as for firefox itself. I don't know about you but "tens of megabytes" seems like a lot to me for a single feature. And I'm not saying fastback is the cause of the large memory uses everyone sees - but it is the item given blame by everyone in response to their complaints about memory.
I'm simply saying that either the justification (fastback's fault) for memory usage is incorrect, it is correct and we just have to accept that it's enormous or the justification is wrong and there really is some problem somewhere that a ton of people are experiencing and that is being sloughed off.
My computer is over 3 years old. It was just a regular midrange Dell. At the time, 512MB was standard and I got 1GB due to a special offer. For people whose computers weren't found in a dumpster, it is definitely worth the hundreds of megs of ram to get a slightly faster back button.
I was actually going for more of a sense of situational irony; however I admit not much thought went to the wording at the time. The best part has been the enjoyment of reading through all the comments about my statement. Isn't that just a little bit ... ironic?
The only ironic thing in her song is that despite being about irony, there is in fact no irony in it. Maybe that was part of the intent of the song in the first place, but it doesn't change the fact that there isn't a single correct use of irony in the piece, just a lot of depressing coincidences.
Mozilla has totally failed to understand the user's priorities
Many many user are trying hard to use firefox Because
1) Too Slow if you install even 10 or 12 Extensions
2) No page zoom facility
3) Extension Technology needs a overhaul Because it Inherently Insecure
Instead of fixing these damn things what are those Mozilla hackers upto i don't understand
Does anyone else suddenly have an urge to play some Gran Turismo 3?
Anyone got any of the GP Alphas to work on Windows Server 2003 (SV1)? Every one of them has invariably crashed just after opening the first window for me.
(OTOH XP and Linux seem fine.)