Hey Folks,
There is lot of hype/expectations around HTML 5.0. So I was looking for more details about new features in HTML5.0 & also how these features will be working in various browsers.
I think Geo location is/will be the one of the hottest topic/feature, I found one good article about HTML5 and its features…. Surprisingly this link is coming from Samsung’s developer forum aka Samsung Mobile Innovator..(I didn’t know that Samsung is also supporting/influencing HTML5.0 features so that their mobile browsers can support rich web experience… Samsung that’s the way to go….. )
The code details given were very useful. I hope this will be helpful for all other HTML and mobile widget/application developers.
All the details you can find here http://innovator.samsungmobile.com/cms/cnts/knowledge.detail.view.do?platformId=12&cntsId=7260
Some of the details covered the above article:
Article Tag
The Article element represents an independent section of a document, page or site. For Ex: Articles are suitable for contents like news, blogs, forum posts or individual comments.
File Browsing
Input type File attribute is used for browsing the files present on the phone or pc. This is not supported on Mobiles. For Ex: The below given image shows the clear description how it works.
Geo-location using HTML5
This feature supported on web. This feature is not supported on wave device.
function showMap(position)
{
alert(position.coords.latitude, position.coords.longitude);
document.getElementById('latitude').innerHTML = position.coords.latitude;
document.getElementById('longitude').innerHTML = position.coords.longitude;
}
Offline Web Application
In order to enable users to continue interacting with web applications and documents even when their network connection is unavailable Ex: when user is travelling outside of the ISP’s coverage area – authors can provide a manifest which lists the files that are needed for the web application to work offline and which causes the users browser to keep a copy of the files for use offline.
You can find full code and details from the above link. Know the new features in easy way.
Please do feel free to share other good links on HTML 5.0 ….
Mod edit: moved from Site Discussion as SD is for topics discussing this site.
So, a mod moved this to a
So, a mod moved this to a different section but didn't remove the obvious spam link?
I don't think it is spam. If
I don't think it is spam. If other mods think it is, they can remove the link.
It's spam albeit slightly
It's spam albeit slightly higher class spam than is normal. Just look at his other post almost identical layout with same link to somesong
He will be history when I get
He will be history when I get back!
Account suspended. two posts is plenty thank you
The spammer does introduce an
The spammer does introduce an interesting topic aside from the Samsung stuff. I recall reading in some blog or another that the mobile industry is heavily vested in html5, with Opera, Android and Apple leading the way. Only MSFT are dragging their heels.
Among the mainstream browsers, again MSFT are lagging behind, though IE9 has a bit of support.
See Lifehacker for a nice summary. Follow their links for more detailed info. Among the more interesting are discussions regarding the video element and arguments regarding h.264 vs ogg/theora+vvorbis.
Since I'm a Debian Gnu/Linux and Firefox user, you can imagine where my prejudices lie.
cheers,
gary
I had noted the their
I had noted the their interest in html5 but with some cynicism. I guess the video aspect is one major factor, however I don't quite get how you build on a specification that ten minutes ago was shrouded in in fighting and anyway wasn't proposed as a rc till ~2030 and why is that embed tag back in favour why was it deprecated in the first place? Do any of these people actually give a hang for the real world?
Cow paths and all that
I think you have it backwards, Hugo. The problem is that optimizing and expanding html toward making an ideal specification are put on the back burner in favor of legitimizing whatever silliness is out there that the browser vendors are already supporting for backward compatibility; paving cow paths run amok.
cheers,
gary