I know everyone is excited about softpress’s implementation of HTML 5 in Freeway Pro 6. Does that mean it’s safe to design new websites with HTML 5 coding or are there still a lot of browsers out there that don’t recognize HTML 5?
Have been for over a year. The HTML5 design team made sure HTML5 was backward compatible with modern browsers, and there’s been a JavaScript “shim” for browsers like IE < 9 that don’t know how to render the new block elements for years. (Freeway 6 includes this automatically.)
Walter
On Feb 1, 2013, at 8:34 AM, RavenManiac wrote:
Thanks Dave. That was very helpful. According to the charts, it looks like HTML 5 is fairly well supported amongst most of today’s browsers.
Consider well that your typical Windows user has a pretty stubborn mentality. As such, a surprising number of Windows users are still using Windows XP (especially here in uber-stubborn Japan). The newest version of Internet Explorer, which unfortunately is about the only browser the stubborn Windiws users tend to use, is version 8. They cannot upgrade to IE9 on XP. So until Windows XP falls exclusively into the domain of computer history textbooks, we really do need to test our sites and structure them for basic compatibility in IE 8.
Also consider that Freeway 6 has a dedicated IE8 page compatibility mode, which shows that SoftPress understands the need to support these pathetically old browsers a bit longer.
And here is a handy tool to navigate the changing webscape -
There’s more, but get started NOW (everyone!!!) reading about HTML5,
learning what is unique and experimenting. I absolutely love it, and wish
Softpress would - at least - build in as much features and support for it
that Walter did AGES ago with his HTML5 actions. (Walter, still love you
for that
Maybe I needs to start me a gripe list so’s they know what I’m seriously
missing >:-)
–
Ernie Simpson
On Tue, Mar 12, 2013 at 4:32 PM, RavenManiac email@hidden wrote:
So, what’s the consensus on this? Is it okay to start outputting my pages
in HTML 5 or should I use XHTML 5?
BTW, I’m currently outputting my sites as XHMTL 1.0 Strict. Will there be
any issues, syntax or otherwise, when I change the coding to HTML 5?
And here is a handy tool to navigate the changing webscape - http://caniuse.com
There’s more, but get started NOW (everyone!!!) reading about HTML5,
learning what is unique and experimenting. I absolutely love it, and wish
Softpress would - at least - build in as much features and support for it
that Walter did AGES ago with his HTML5 actions. (Walter, still love you
for that
Maybe I needs to start me a gripe list so’s they know what I’m seriously
missing >:-)
Ernie Simpson
This is good stuff. I’m reading the book from your first link now.
Suppose I convert my XHMTL 1.0 Strict websites to HTML5 and my client gets compatibility complaints from users, can I simply flip the FWP output switch back to XHMTL 1.0 Strict and re-upload my files or is this a one way trip?
Just because of these kind words, and because I’d been meaning to, I just revved all of my HTML5 Actions to work with Freeway 6. All I did was add a guard clause around the function that rewrote the page (DOCTYPE and parts of the head) from XHTML to HTML5. They still do things you can’t do ordinarily in Freeway 6.
Walter
On Mar 12, 2013, at 10:37 PM, Ernie Simpson wrote:
and wish
Softpress would - at least - build in as much features and support for it
that Walter did AGES ago with his HTML5 actions. (Walter, still love you
for that
Yes you can, but no you won’t. HTML5 is designed to work with all the browsers that are out there now (with a polyfill for the new block objects, which Freeway provides). The only browsers that will have trouble with these pages will be browsers that would have problems with any modern page. Netscape Navigator 4, maybe, or IE 5. Anybody still using those has much larger issues, like where to find gas for the generator, and chicken wire to patch the satellite antenna.
Walter
On Mar 12, 2013, at 11:43 PM, RavenManiac wrote:
Okay, here’s a followup question.
Suppose I convert my XHMTL 1.0 Strict websites to HTML5 and my client gets compatibility complaints from users, can I simply flip the FWP output switch back to XHMTL 1.0 Strict and re-upload my files or is this a one way trip?
For every 50’ of chicken wire you buy from me I’ll throw in a free chicken. And not just any chicken, one of those struttin’-around, high-falutin’, fancy cluckers. Nuttin’ but da best fer my Netscape clientele.
For every 50’ of chicken wire you buy from me I’ll throw in a free chicken. And not just any chicken, one of those struttin’-around, high-falutin’, fancy cluckers. Nuttin’ but da best fer my Netscape clientele.
Todd
I knew Walter’s comment was too good for you to resist.
I spent the last few summers on a cattle ranch 45 minutes from the nearest small town, an exact replica of the one Walter described. One of my jobs during this last time was to try and clean up their ancient XP so that it would be usable, which was used by the husband for occasional tractor part shopping and the wife for pictures. (The camera card hadn’t been dumped in a year or so, and she was having to delete older pictures to get more space.)
Now, that was a project.
A combination of about 10 toolbars for IE, an HP software “assistant” that popped up every 5 minutes of use, super-slow dialup, and all the junk their son had installed made it a feature-length undertaking.
I wanted to install Chrome but the estimated download time was one week and that would mean no phone calls, not that we would miss them in particular.
Yes, chicken wire was a much more pressing issue for us. Oh, and I’m sure the wife will take you up on your deal Todd, but watch out! She’ll get you to shake on a deal where she gets your whole flock of chickens, 50ft of chicken wire, and your kitchen sink for less then the cost of the wire.
Oh, and I’m sure the wife will take you up on your deal Todd, but watch out! She’ll get you to shake on a deal where she gets your whole flock of chickens, 50ft of chicken wire, and your kitchen sink for less then the cost of the wire.