11–20 of 75 posts
And yet... you can use it to visit maps.google.co.uk [0]. Stop making excuses for Google. This is ridiculous ffs. [0] http://www.youtube.com/watch?v=_Z8vfzurnKw
Bizarre. I wonder if, in 10 years, WebKit will be viewed as the next IE6 when the latest/greatest HTML rendering engine comes along? What happened to standards compliance?
WebKit is constantly moving forward, and is not stagnant like IE6 was. Many of its initially-proprietary web features have been standardized and adopted by other browser engines. The primary challenge is convincing web authors to support the standardized versions of the formerly-proprietary features alongside the browser-specific versions.
How come it's OK for WebKit to extend the spec with non-standard features but it was not OK for IE 6? Sure, some of the features have been standardized and included in other browsers, but the same thing happened with IE! You can thank IE for the XmlHttpRequest after all.
I can literally see no difference between IE6 adding non-standard features vs. WebKit doing it. You just have personal stake in WebKit succeeding and don't want to admit it's basically the same thing.
Bizarre. I wonder if, in 10 years, WebKit will be viewed as the next IE6 when the latest/greatest HTML rendering engine comes along? What happened to standards compliance?
Honestly I think the title is just PR BS from Google. You can use WP8 browser to access maps.google.co.uk and it works perfectly fine [0] [0] http://www.youtube.com/watch?v=_Z8vfzurnKw
And yet... you can use it to visit maps.google.co.uk [0]. Stop making excuses for Google. This is ridiculous ffs. [0] http://www.youtube.com/watch?v=_Z8vfzurnKw
Note that the video shows the user able to access the desktop version, but the article is about accessing the mobile version. Here's what the mobile UI looks like: http://i.imgur.com/oCveo.png
I don't ever remember Google Maps being blocked in Konqueror or IceCat, so I'm not sure why they are using this tactic on mobile. More importantly, a lot of good-citizen webdevs work at Google like Paul Irish, must be rather awkward for those types.
On the other hand, isn't the whole point of web standards to avoid situations like this?
I suspect we'll just get confirmation of something we really already know: standards are really important only when you're not the market leader.
And yet... you can use it to visit maps.google.co.uk [0]. Stop making excuses for Google. This is ridiculous ffs. [0] http://www.youtube.com/watch?v=_Z8vfzurnKw
Bizarre. I wonder if, in 10 years, WebKit will be viewed as the next IE6 when the latest/greatest HTML rendering engine comes along? What happened to standards compliance?
The reason its not supported is not because of technological limitations. It's just anti competitive practices from Google.
They probably figure if they let Google in on some things, then they open the door to supporting all of Google's apps like gmail, chrome, calendar, google docs, etc. Which goes against them wanting people to use outlook.com, their calendar, MS office and IE as their main browser.
Earlier quoted context omitted.
WebKit is constantly moving forward, and is not stagnant like IE6 was. Many of its initially-proprietary web features have been standardized and adopted by other browser engines. The primary challenge is convincing web authors to support the standardized versions of the formerly-proprietary features alongside the browser-specific versions.
Personal bias much? I see you work on Safari at Apple. How come it's OK for WebKit to extend the spec with non-standard features but it was not OK for IE 6? Sure, some of the features have been standardized and included in other browsers, but the same thing happened with IE! You can thank IE for the XmlHttpRequest after all. I can literally see no difference between IE6 adding non-standard features vs. WebKit doing i…
Historically, IE's new features have been developed for IE and Windows only. Then when competition had been sufficiently smothered, development on IE was simply halted.
