Safari right now does support HTML 5 - it just doesn't contain every feature that the spec supports just yet - remember the details of HTML 5 have not been locked down yet so all browsers that support HTML 5 are doing so in a hitting a moving target scenario.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Steve Jobs Promises Full HTML5 Support for Safari 'Soon'
- Thread starter MacRumors
- Start date
- Sort by reaction score
Safari right now does support HTML 5 - it just doesn't contain every feature that the spec supports just yet - remember the details of HTML 5 have not been locked down yet so all browsers that support HTML 5 are doing so in a hitting a moving target scenario.
Meh, Apple needs to get full-screen HTML5 support in their browser before they can think about enhancing mobile Safari.
Not sure if you watched the last Apple Event but ALL the iAds were made in HTML5.
Let go of the past (Adobe Flash) it's old technology, by a lazy company.
Uhm, who cares? With HTML5 and GeoLocation, we will get the same thing through the browser.
Edit:
And, here is an example: http://html5demos.com/geo. Of course, in OS X you can't test this in Safari yet. But, you can if you have Chrome or FF. Also, works in Safari for iPhone OS.
Just like a parrot repeating everything you hear, but yet you don't even know why you're saying it.
WebKit Nightly
Anybody can get the latest version of "Safari" via the WebKit Nightly builds. And they don't need to be bothering an extremely busy CEO in order to find out what the plan forward is for WebKit-based browsers. It's an open-source project. Geesh!
http://www.webkit.org/
Anybody can get the latest version of "Safari" via the WebKit Nightly builds. And they don't need to be bothering an extremely busy CEO in order to find out what the plan forward is for WebKit-based browsers. It's an open-source project. Geesh!
http://www.webkit.org/
Uhm, who cares? With HTML5 and GeoLocation, we will get the same thing through the browser.
That may be the case, but Maps are much better as Applications instead of for browser use at the moment.
What your talking about is 2013 and beyond.
Flash was created during the PC era for PCs and mice. Flash is a successful business for Adobe, and we can understand why they want to push it beyond PCs. But the mobile era is about low power devices, touch interfaces and open web standards all areas where Flash falls short.
The avalanche of media outlets offering their content for Apples mobile devices demonstrates that Flash is no longer necessary to watch video or consume any kind of web content. And the 200,000 apps on Apples App Store proves that Flash isnt necessary for tens of thousands of developers to create graphically rich applications, including games.
New open standards created in the mobile era, such as HTML5, will win on mobile devices (and PCs too). Perhaps Adobe should focus more on creating great HTML5 tools for the future, and less on criticizing Apple for leaving the past behind.
So actually I do know why Im saying this. Let go of the past my friend stop being lazy and accept the fact that Flash is a PC space technology not a Mobile Space one.
You mean he's actually pushing something that's theoretical in his browser? Something else that he can't get working right yet? So, Flash isn't the only thing he's having trouble with? I'm surprised.
Im a bit confused, I use WebKit and have had no problems on my Mac when it comes to Youtube HTML 5 Beta, am I missing something or is Apple Safari the one that is way behind.
Safari 4 has an incomplete implementation of HTML5 - partly because the spec isn't complete.
how about this: developed with flash since it was called future splash animator, won awards for flash work, spoken at conferences on flash work, written books about flash, created and taught curriculum about flash at three universities, part of alpha, beta and gold master teams for various releases of flash.
- adobe was lazy. i haven't participated in an alpha/beta for a long time after being thoroughly disgusted with my last experience and how little they cared about putting out a buggy release. i have no idea about their current work ethic, but based on running cs5 through its paces there are bugs and interface issues that have existed since the 90's.
- though flash is not dead, nor will it be for some time to come. this is not because html/css/js cannot accomplish a great deal of what flash can, but because there is no current visual development environment that caters to designers/animators and target audiences/platforms are too small. once that changes the flash player as a delivery mechanism will drop off sharply
- html5/css/js can today accomplish 70-80% of what flash is used for on the web today (banner ad, videos, transitions, etc…). there are sites like http://www.gettheglass.com/ that would be too time consuming to develop in html5/css/js and also not have the delivery platform to make the development costs worthwhile, but as ie9, chrome5, firefox4 and safari5 start getting released it will become more feasible
- as mobile devices continue to expand and standardize for the most part around webkit (android, palm/hp, apple, rim, some symbian devices) the benefits of flash become far less apparent while the drawbacks (security problems, performance, battery issues, etc…) become more of a problem. it doesn't matter how much adobe tweaks the flash player, it's always going to be a process that runs above native processes in the device/computer. it has and will gain more access to some low level hardware, but it will never compete with native processes.
- tied in to mobile adoption, the primary driver of flash (after the initial experimentation exemplified by the likes of josh davis and yugo nakamura) have been advertising agencies, they're the ones who have the money to fund big experiences. they need as many eyeballs as possible, as mobile viewership continues to take off they will need to create content for mobile devices. the experience on mobile will need to be optimized for touch and small screens so it will likely be an entirely different development from the main experience. two major repercussions from this:
- the short term effect will be if you're developing a second experience for mobile, you're not going to ignore large demographic like iphone users. so ad agencies will end up opting for an html5 solution for mobile.
- as developers/designers get more and more comfortable designing these mobile experiences and the experiences themselves become more and more advanced you'll see a halo effect; agencies will want to streamline their development cycle, sharing assets, code, and personnel will be much easier when the entire project is completed in html5
- flash cs6 will offer the option to export has html5 and that will be the death knell for swf. adobe will be in a tough position because they'll not want to give up their control of multimedia delivery on the web, but the won't want to give up their dominance of multimedia creation - which is where they make their money.
Great point - Jobs really has to put his money where his mouth is, it'll look pretty bad if another browser does a better that job with HTML5 than Safari.
P.
Good thing you weren't talking about spelling, because you spelled GRAMMAR incorrectly.
Actually, you were trying to correct the grammar, but your own spelling and grammar got in the way, eh?