This test does NOT test full CSS2 compliance. I understand this should test full CSS2 compliance.
#Ffworks mac how to#
MS will need to learn how to work together with the other browser developers or they will loose even more users.įollowing some links, starting from this article I got onto ACID2 test page. It’s costing us a lot of time and money to develop websites in the current environment. 10% of all the webbrowsers out there is a lot of browsers.
#Ffworks mac professional#
And that’s not fair competition to me.Īlso if IE is the standard, then why are all professional web developers trying to develop for every browser out there? Perhaps because IE isn’t the only player.
All the others will have to guess what microsoft is up to next and try to implement it as quickly as possible. Especially since that standard is poorly documented and under closed development. It’s a pretty stupid idea to let the product that has the largest marketshare set the standard. That is possible if everyone follows one standard. I’d like to be able to give my clients a website that will work as expected for at least five years. If I build websites for my clients around IE, then what would happend if suddenly two years later Firefox is the most popular browser? Well, the thing is that I can’t know that IE will be the standard browser in a couple of years. IE’s way of doing things is a standard, as the majority of people USE IE. They certainly have a lot of room to improve, so anything would be a step in the right direction, it’s when we actually see results from these steps that we can say microsoft is actually doing something right security wise. It sounds like with steps like LUA microsoft is finally moving toward the right direction. I’m not neccesarily going to comment on how ie7 or longhorn are going to improve on it. Simply put, I’m not a security expert or a web browser designer, but some things microsoft should be able to do are: use better default security policy, allow easy overriding of security policys with appropriate warnings, remove technoligies that are redundant and prone to security errors(such as activex), unintegrate ie from the rest of the system(why shouldn’t I be able to run ie in it’s own little sandbox under user guest or something like that).Īs for SP2, it’s a good step, but if users don’t understand why something stopped functioning and one of their friends tells them to disable the firewall on the ethernet device to make it work, they are just going to do that, if they can’t find an easy way to get the features they expect to work working(AIM file transfer, VNC, a game server, ping).
Don’t be an elitist about it and blame it on the users.
Users shouldn’t have to be technically oriented or a security expert to be able to avoid all the malware that is out there. Users eventually end up discovering that if they listen to all these “oh my god” messages they can’t do anything they expect to be able to do, they don’t understand the techno mumbo jumbo ones, and if something is just blocked “because” and something isn’t working the way they think it is they do whatever they can to make it work, regardless of warnings. Users generally read the warnings the first time, but have you actually read a lot of the warnings you get in IE? Some of them are just techno mumbo jumbo, some of them just explain that something was not displayed “because”, and some of them are like “Oh my god! run away”. >what specifically would you like them to do? Users need to >take responsibility for failing to read warnings Heh, btw is this the innovative new way of using the web they were talking about a couple of months ago? That was what IE7 was supposed to be all about right? So I still fear that I’ll have to do ugly hacks to keep websites looking good in all browsers. Does that mean following Mozilla?īecause even if they follow the W3C specs, those specs doesn’t say how things are supposed to be rendered exactly, we might still end up with things like the annoying box-size problem (which I actually think MS did right, but someone has to fold). Why couldn’t they just have done it right from start instead of fixing it years later? Oh right, that’s the microsoft way of doing things.Īlso, I’m curious, they mention that they will make CSS support more consistant. But we still have to consider all the IE6 users out there, which will be plenty, even years after IE7 has been released. Personally as a webdeveloper I’ve been wanting to hear that noone is using IE anymore and that Microsoft has quit developing it.
0 kommentar(er)
