It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Community
General discussionFirefox 3.0.7 is out(25 posts)(25 posts)
(25 posts)
Pages:
1
2
This is my favourite topic
Posted March 06, 2009
avatar
Ois: Open Font Library. Last I checked, there was not much there, but it's a start.

Thanks... I was really looking high and low but somehow I managed to miss that one.
Posted March 06, 2009
I don't see animations as such a bad thing, but I suppose I haven't looked at the way they did it as well as you.
I suspect that publically-licensed fonts may start to become more common once there is a practical use for them. This is one of the reasons I'm happy that the font support is arriving.
Posted March 06, 2009
avatar
Barefoot_Monkey: I don't see animations as such a bad thing, but I suppose I haven't looked at the way they did it as well as you.
I suspect that publically-licensed fonts may start to become more common once there is a practical use for them. This is one of the reasons I'm happy that the font support is arriving.

It's just that CSS animations would promote a second standard that does nothing but duplicate (spec-wise, Firefox doesn't support SMIL) existing functionality. I'd rather stick with the current JS workarounds a bit longer and when it's finally all working, end up with only two sets to maintain: the SMIL code and the JS workaround. Otherwise, I'll have to check for CSS animations, then fall back to SMIL and finally to JS and static CSS. 25% more work without any real benefit.
P.S. If you want to use something like this now, I have a function that does it somewhere in my toolKit with few dependencies (I think only hardScope which doesn't have any dependencies at all). I can post it if you want.
Post edited March 06, 2009 by hansschmucker
Posted March 09, 2009
avatar
hansschmucker: It's just that CSS animations would promote a second standard that does nothing but duplicate (spec-wise, Firefox doesn't support SMIL) existing functionality. I'd rather stick with the current JS workarounds a bit longer and when it's finally all working, end up with only two sets to maintain: the SMIL code and the JS workaround. Otherwise, I'll have to check for CSS animations, then fall back to SMIL and finally to JS and static CSS. 25% more work without any real benefit.
P.S. If you want to use something like this now, I have a function that does it somewhere in my toolKit with few dependencies (I think only hardScope which doesn't have any dependencies at all). I can post it if you want.

If you don't mind posting then I'd love to see how you do it.
Personally I prefer not to maintain multiple implementations at all. Just describe the animations once in CSS and everyone whose browser happens to supports it will see animation. 75% less work and everyone's happy.
Posted May 13, 2015
low rated
...
Posted May 13, 2015
avatar
nekoai: ...
That may be the most pointless necro post I have ever seen.
Posted May 13, 2015
Hey ;=
Posted May 13, 2015
A Zombie thread, great. I wish Worf der Grosse would be a member of the GoG forum, he would very appreciate that!
Posted May 19, 2015
damn I'm only on version 38.0
Posted May 19, 2015
avatar
ChloeWolfieGirl: damn I'm only on version 38.0
Really? That version was pulled on the day it was released because of a serious bug. I suggest you update to 38.0.1.
Pages:
1
2
This is my favourite topic
Community
General discussionFirefox 3.0.7 is out(25 posts)(25 posts)
(25 posts)