Lets see, since somebody already stated Im too stupid... I will just try my best to explain 
Webkit... ok, obviously you should know webkits is a fork of KHTML, I have no problem with the idea that KHTML was created to promote OSS. But why was webkit created? and why was safari created?
Webkit, as a fork, has no position to claim "built from the ground", this is first point, next point is: apple established webkit, and announced safari, becasue, IMHO, the development if IE on mac was stalled. Apple grabbed KHTML and built a browser in hope of not lagging too much behind and w/o a decent browser. Was "openess' a thing in apple's mind? IDK, and I think you dont know neither.
Its not webkit need less work in order to pass the test, its it didn't pass any meaningful thing, it tells web developers it passed, but when developers use those standard, the result would be a no, its confusing and not helpful
I guess when they said "created to", that means they started from that goal.That's right. Webkit promotes openness, innovation and opportunity of the web and Safari, which uses the Webkit rendering engine in turn promotes openness, innovation and opportunity of the web. This applies to any other browser which uses Webkit as its engine.
Webkit... ok, obviously you should know webkits is a fork of KHTML, I have no problem with the idea that KHTML was created to promote OSS. But why was webkit created? and why was safari created?
Webkit, as a fork, has no position to claim "built from the ground", this is first point, next point is: apple established webkit, and announced safari, becasue, IMHO, the development if IE on mac was stalled. Apple grabbed KHTML and built a browser in hope of not lagging too much behind and w/o a decent browser. Was "openess' a thing in apple's mind? IDK, and I think you dont know neither.
yes. thats goodThere are lots of examples.
This is great. Obviously they are on to something good. You missed off Google's Android as well, which will also use Webkit.
Glad we're agreeing so far.![]()
well, lets say, a standard passed W3C, which contain 54 items for web developers to utilize, Opera support 50 of those 54 items, while safari only support 3 of them. Why? because acid 3 can't check every item, so it only check few items of each standard, and webkit just did so to pass the test.Please explain.
Why not? They are competing browsers. They use different rendering engines and both of those have got full marks in ACID 3.
Thats not real pass, don't you see? when you only implement 5 items out of 54 of a standard, web developers can't use it!, It has no meaning in helping the web environment!Normally you measure performance by how good something is, not how much work went into it. Webkit needed less work to it in order to pass, so what? That just means it started out better in the first place.
Its not webkit need less work in order to pass the test, its it didn't pass any meaningful thing, it tells web developers it passed, but when developers use those standard, the result would be a no, its confusing and not helpful
It is important to have a test, but ppl need to regard the test with some realistic ideas. Acid3's standard enclosure has a deadline of 2004, do you think there is no change in past 4 years and all the standard remain the same? NO, Acid 3 also include some standard that since been altered, updated, or abolished, in that case, NOT pass is a better result than pass.Of course no measurement is perfect. It is better to have some measurement than none. If Mozilla are not happy with the ACID tests then they should create there own tests and push for these to be used to determine support of standards instead.