Hi,
have you got any problem with it? I have one testpage that parses my ordered list in wrong way with using FF3 but with IE7(cant believe im writing this) it works like it should!
Cheers:
- Tuittu
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
July 18, 2008 4:33am
Subscribe [6]#1 / Jul 18, 2008 4:33am
Hi,
have you got any problem with it? I have one testpage that parses my ordered list in wrong way with using FF3 but with IE7(cant believe im writing this) it works like it should!
Cheers:
- Tuittu
#2 / Jul 18, 2008 4:52am
No, FF 3 is great. Much better than FF 2, in fact.
#3 / Jul 18, 2008 4:56am
Yeah and what comes to my problem. For some odd reason i didnt doublecheck my own codes and more interesting, the page did work as it was ment to work, earlier but not anymore. anyway, i opened it and cleaned and boom, now it works with FF3 also =)
Strange days…
- tuittu
#4 / Jul 18, 2008 5:05am
In terms of CSS both Firefox 2 & 3 are to the letter with CSS.
Do you reset your CSS padding and margins before you start? If you don’t try Eric Meyer’s Reset.
It gives you a common starting point and removes the different interpretations of browsers in terms of padding, margin and a few other things.
In short though FF3 rocks!
#5 / Jul 18, 2008 11:21am
In terms of CSS both Firefox 2 & 3 are to the letter with CSS.
That should be clarified to read: In terms of CSS that they support both Firefox 2 & 3 are to the letter with CSS. I was shocked to find that most CSS3 selectors and features still aren’t implemented even with the experimental -moz attributes in the FF browser family. Here’s hoping 3.1 does.
#6 / Jul 18, 2008 3:16pm
I’ve been running 3.1 for a while now, and it is a lot more stable on my system than 3.0 was. I think maybe once I’ve had 3.1 shut itself down spontaneously, as opposed to about once a day with 3.0
Added: Grrrrrr. I posted too soon. @#$!!
#7 / Jul 18, 2008 3:38pm
I wasn’t aware it was available for download yet, McGehee. Looks like it addresses some of my CSS3 gripes, but still no support for @font-face. ::sigh::
#8 / Jul 18, 2008 3:57pm
So <font face=”“> is not good enough, hm? 😛
#9 / Jul 18, 2008 4:07pm
I know you post in jest but I can’t resist pointing out that that’s not the same purpose. The deprecated evil font tag just handles things that the font: CSS attributes do. @font-face allows you to create a new font for use in the font-family attribute, including setting default weight and pointing to a URL for the source of the font file, allowing you to use any font you have license to use, regardless of whether it’s installed on the visitor’s computer.
#10 / Jul 18, 2008 4:11pm
Wow, really? So it’s basically server-side font handling?
#11 / Jul 18, 2008 4:15pm
Thanks for clarifying, Derek. Of course I was joking, yes 😊
#12 / Jul 18, 2008 4:21pm
Wow, really? So it’s basically server-side font handling?
Yep, here’s an example from my personal site on a web browser that supports it and one that doesn’t.
#13 / Jul 18, 2008 4:58pm
Well that’s the dawn of a new era. How slim is the support for it?
#14 / Jul 18, 2008 5:00pm
Very early days still.
#15 / Jul 18, 2008 5:01pm
Just WebKit at present. FF 3.1 and Opera 10 have it marked as planned.