Well the web needed a means of setting the viewport scale, and the one Apple came up with is as good as any.
Are you really insistent that you come op with your own "-moz-viewport" crap just because there isn't a draft standard? The vendor prefix bullshit of the last few years is going to be around for at least another decade, with every CSS3 property being set three goddamn times because the vendors will have shipped support for the prefixed version for several major releases before they think about blessing it. I wish y'all would only do that stuff in beta releases to keep it out of the wild.
Setting the viewport doesn't require anything like trampolining through VBScript, loading an ActiveX control, or calling a DirectX function via VML (all things I've had to do recently). MobileSafari is not the new IE.
Have fun being another legacy browser on a slow release cycle that can't ship a decent mobile browser.
> Are you really insistent that you come op with your own "-moz-viewport" crap just because there isn't a draft standard?
No, we're not insistent. We implemented WebKit's "viewport" meta tag. We can be pragmatic too.
I just wanted to point out one of the many of Safari features that Apple is promoting without writing any specs or standards, and the effect this has on the browser market. Others include touch events, link[rel="apple-X"], -webkit-text-size-adjust...
I agree the proliferation of vendor prefixes in the wild has bad effects, and we are feeling the pain of it too.
----
> Have fun being another legacy browser on a slow release cycle that can't ship a decent mobile browser.
Thanks for the kind words. :) We know we're way behind the game on mobile, and the only thing we can do to fix it is ship great software. I think when you get a chance to see what you can do with add-ons for mobile Firefox, you'll be tempted to switch.
We're on a rough six-month release schedule: Fennec 1.0 shipped in January, Fennec 1.1 will ship this month, and we are targeting this October or November for Fennec 2.0. Look for our first 2.0 alpha release for Maemo and Android in a month or two.
[P.S. I see you're in Seattle too! Want to get together for coffee sometime? Email me if you do.]
> The vendor prefix bullshit of the last few years is going to be around for at least another decade, with every CSS3 property being set three goddamn times because the vendors will have shipped support for the prefixed version for several major releases before they think about blessing it. I wish y'all would only do that stuff in beta releases to keep it out of the wild.
Are you really insistent that you come op with your own "-moz-viewport" crap just because there isn't a draft standard? The vendor prefix bullshit of the last few years is going to be around for at least another decade, with every CSS3 property being set three goddamn times because the vendors will have shipped support for the prefixed version for several major releases before they think about blessing it. I wish y'all would only do that stuff in beta releases to keep it out of the wild.
Setting the viewport doesn't require anything like trampolining through VBScript, loading an ActiveX control, or calling a DirectX function via VML (all things I've had to do recently). MobileSafari is not the new IE.
Have fun being another legacy browser on a slow release cycle that can't ship a decent mobile browser.