You're not wrong, but think of it this way:
As long as this is the current state of things with WebKit, the counterweight to that is that Apple ultimately gets veto power over any standard the rest of the industry does agree on, and random HTML and CSS features will sit functionally unusable for years because a single OS vendor doesn't see them as a priority.
The problem that we're both ultimately getting at here is that one vendor shouldn't get to have a chokehold on the spec. With Safari it just happens to be closer to what was wrong with IE.
>the rest of the industry does agree on
The "rest of the industry" is functionality just Google. The only reason Google pretends to care about "standards" is because of the large amount of iOS users on WebKit. That evaporates when Google, via Chromium has complete control of the web platform.