http://www.mozilla.org/projects/firefox/3.0a2/releasenotes/
Since I know how much you lot love living on the bleeding edge of technology.
/me downloads
/me too scared You're just
/me too scared
You're just sooo avant guard TPH
Oh, it's awful. I've
Oh, it's awful.
I've already thrown it out.
Wait for beta.
http://www.mozilla.org/projec
http://www.mozilla.org/projects/firefox/3.0a2/releasenotes/
Firefox 3 Alpha 2 available.
I wonder why they've skipped straight past 2.5 and gone for 3?
One nice thing is full Acid2 compliance. That'll stop all those FF-bashers complaining that we don't do Acid2 properly
Lets hope they finally fix
Lets hope they finally fix Bugzilla #87277 - Firefox's completely unimplemented vertical margin collapse on tables
Have they also got around to
Have they also got around to the fixing the position of the background of the element which creates a new stacking context?
Why what was/is wrong with
Why what was/is wrong with it? test case please
Ha notice Gary involved in that bugtrack and of all people to admit to not RTFMing
You'll need to search for my
You'll need to search for my various replies on z-index in the past for the test case
The background of the element which creates the stacking context is the canvas on which the whole stacking context is drawn. That is, nothing in the stacking context can appear behind it. FF (up to now) has always drawn the background as the lowest item with a z-index of 0. ie, descendants with negative z-index will be drawn behind that background.
FF's behaviour makes it impossible to place something between the foreground of the the stacking context creator and its background.
There you go with the damn
There you go with the damn winks again :mad:
I'm with you, don't need to see a test case, this was the object of my confusion a while back when stating that where on earth was negative stacking meant to go but behind and therefore out of sight of '0'
Now I'd run along and get some Optrex for that eye!
Hugo wrote:Ha notice Gary
Ha notice Gary involved in that bugtrack and of all people to admit to not RTFMing
I am nothing if not honest about my shortcomings. There being so few, they tend to stand out.

cheers,
gary
kk5st wrote:Hugo wrote:Ha
Hugo wrote:Ha notice Gary involved in that bugtrack and of all people to admit to not RTFMing
I am nothing if not honest about my shortcomings. There being so few, they tend to stand out.⇐ wink
cheers,
gary
That is exactly what I was thinking as I read your comments, I thought to myself " well what do you know there's Gary, he'll set things straight, he's got so few shortcomings", then lo and behold and a sharp intake of breath as I realised he hadn't read the F******* manual, of all the faux pas to have committed and the one shortcoming that he had to offer and there it was in all it's glory, tis a sad day.
thepineapplehead
I wonder why they've skipped straight past 2.5 and gone for 3?
Generally speaking (as I understand it), point updates of software (e.g. 2.3 to 2.4) consist of modifications, enhancements and bugfixes, whereas integer updates (e.g. 2.3 to 3. involve major changes to the core scripts or 'engine' i.e. a complete rewrite.
Hmm... I have had Gran
Hmm... I have had Gran Paradiso 3 alpha 3 for some time now, and as I understand it that's what is supposed to be the latest release of what will eventually be called Firefox 3. I posted about it some weeks back.
Have they changed the name or something?
Gran Paradiso (afaik)is
Gran Paradiso (afaik)is still the name they're using for the stable(ish) alpha versions of Firefox 3, however I've moved on since then, I'm using the nightly builds, codenamed Minefield It's up to Firefox 3 Alpha 5 Pre