how do you guys like HTML5
- Thread starter DotCom
- Start date
CaldwellYSR
Member
doh!
Anyways... HTML5 is great although I don't use it as much as I want to. I really want to get into <canvas> and things like that but haven't found an excuse yet.
AsheSkyler
New Member
I like the designated header and footer tags. I haven't really had a chance to play with all the other stuff.
I've been using the audio and video tags for some time although you still need to provide flash fallback for older browsers.
Its really easy to make video responsive using html5 but you still need to use media queries to load different file sizes for the various devices.
Audio is still not very well supported natively - especially by Firefox - so I still use mediaelement by John Dyer for single tracks.
Its really easy to make video responsive using html5 but you still need to use media queries to load different file sizes for the various devices.
Audio is still not very well supported natively - especially by Firefox - so I still use mediaelement by John Dyer for single tracks.
I hope you just worded that wrong. Media queries don't change what you load, just how it displays. If you're using them to show different file sizes for videos, you should know that everyone is downloading every version of the file you have, and only seeing the one that is meant for them. That's a lot of bandwidth.
leroy30
New Member
I've been playing around with geolocation a lot lately and I'm quite disappointed.
Although I'm not disappointed with geolocation itself, more the browser implementation of it.
My main beefs in this regard are:
1) Browsers ignore the maximumAge attribute and consistently return cached results from half an hour ago even when I specify do not used cached results. Stupid thing is even if I use a native app to get a more recent location, the browser still serves an even older cached result. I can vouch for this in mobile Chrome and androids default mobile browser.
2) Browsers refuse to use the GPS even when enableHighAccuracy is set to true AND I've used an app to force the GPS to start AND I use watch position. I never ever get a GPS location the best I get is a Cell tower triangulation. This is on Mobile Chrome and Ice cream sandwiches default browser.
3) There should be a way to force the 'allow access' prompt. Many of my customers don't know how to, or are afraid to, change geolocation settings in their browser to allow accidentally or previously disallowed geolocation access for a website. I understand the security implications of the prompt but there should be a way to show the prompt again if they selected disallow. The use-case applies to SAAS that uses geolocation as one of the primary features.
Ok so really I'm more beefing about Chrome and Android than anything else but hey, I need consistency! I don't yet know what it's like on the likes of iPhone.
Although I'm not disappointed with geolocation itself, more the browser implementation of it.
My main beefs in this regard are:
1) Browsers ignore the maximumAge attribute and consistently return cached results from half an hour ago even when I specify do not used cached results. Stupid thing is even if I use a native app to get a more recent location, the browser still serves an even older cached result. I can vouch for this in mobile Chrome and androids default mobile browser.
2) Browsers refuse to use the GPS even when enableHighAccuracy is set to true AND I've used an app to force the GPS to start AND I use watch position. I never ever get a GPS location the best I get is a Cell tower triangulation. This is on Mobile Chrome and Ice cream sandwiches default browser.
3) There should be a way to force the 'allow access' prompt. Many of my customers don't know how to, or are afraid to, change geolocation settings in their browser to allow accidentally or previously disallowed geolocation access for a website. I understand the security implications of the prompt but there should be a way to show the prompt again if they selected disallow. The use-case applies to SAAS that uses geolocation as one of the primary features.
Ok so really I'm more beefing about Chrome and Android than anything else but hey, I need consistency! I don't yet know what it's like on the likes of iPhone.
leroy30
New Member
That's where you need a server-side script that checks the browser headers for known mobile devices so you can anticipate which version to serve
I hate non-consistency. I swear we need to create another organization like the W3C that demands consistency or there will be nothing developed for it. It makes absolutely no sense for something not to be consistent. It is such a waste of time!! You create this beautiful mural of technology, only to be smothered because some un-professional company wants differentiate its self from the crowd.
leroy30
New Member
Don't worry. It will only be a matter of time before Apple decides to create their own, closed loop internet where you'll be able to get your consistency
On the brighter side it gives us extra leverage to separate ourselves from the noobies!
That's where you need a server-side script that checks the browser headers for known mobile devices so you can anticipate which version to serve
Can even be done with client-side coupled with AJAX.
leroy30
New Member
This is true. Probably more robust as well.
Yeah i was playing with CSS3 last night, all i can say is. Thank YOU!!! it's makes the job so much easier and so much less mark up. Some declarations have to be specific for browsers but this is only temporary, like opacity and radius. But targeting has gotten so much simpler.
wow, I take it you haven't read the spec...
http://dev.w3.org/html5/spec/single-page.html
I assume you haven't read it because I draw your attention to section 1.4 HISTORY, and in particular this section. (mind you this is before it actually gets dry, so its actually readable up to this point, so no excuse for not getting to it...)
and now finally it looks as though M$ is getting onboard with html5, standards and w3... YOU want to start it up again with something new!!!