Anybody know why the new less-framey output is called "HTML5"? I can't see any HTML5-specific coding in there. It all looks like XHTML to me. Seems that "HTML5" is a misnomer.
-Paul
Where's the HTML5 in HTML5 output?
Re: Where's the HTML5 in HTML5 output?
Because it doesn't work well with IE8?
I don't know enough about the underlying code - but with larger projects, IE8 simply can't handle it (Chrome and Firefox are fine). Which seems to be a symptom of HTML5.
Some scripts on masterpages aren't working too.
According to Feedback, over 50% of my page clicks are on IE7 or 8 - so "HTML5" is no-go at the moment, until people are forced to upgrade.
Can anyone advise as to the up-side of using HTML5, except the skin looks nice? Having the URL being visible is also useful, anything else?
Thanks
I don't know enough about the underlying code - but with larger projects, IE8 simply can't handle it (Chrome and Firefox are fine). Which seems to be a symptom of HTML5.
Some scripts on masterpages aren't working too.
According to Feedback, over 50% of my page clicks are on IE7 or 8 - so "HTML5" is no-go at the moment, until people are forced to upgrade.
Can anyone advise as to the up-side of using HTML5, except the skin looks nice? Having the URL being visible is also useful, anything else?
Thanks
-
Robotman
- Sr. Propeller Head
- Posts: 186
- Joined: Sat Mar 04, 2006 3:05 am
- Location: Melbourne, Australia
- Contact:
Re: Where's the HTML5 in HTML5 output?
It could be my coding (and it probably is), but viewing images using the traditional webhelp (larger images on smaller screen resolutions) was terrible (the whole image would not be displayed). HTML5 output fixed that instantly. I also like the searching and the modern look (webhelp, like CHM, looks a bit old school).
For those small reasons alone the new output improved things.
As for IE 7 - we've told all clients that they'll need to run IE8 as a minimum (which is free to XP users - our lowest common denominator). Seems to work fine in IE8 and 9 and any iteration of FF.
Though I do completely agree with Paul in his original post but as an improvement over webhelp, it's all good from our end.
For those small reasons alone the new output improved things.
As for IE 7 - we've told all clients that they'll need to run IE8 as a minimum (which is free to XP users - our lowest common denominator). Seems to work fine in IE8 and 9 and any iteration of FF.
Though I do completely agree with Paul in his original post but as an improvement over webhelp, it's all good from our end.
Re: Where's the HTML5 in HTML5 output?
It's possibly called HTML5 because the output uses the HTML5 doctype; i.e. <!DOCTYPE html>
I know they need to differentiate it from WebHelp, but calling the target type HTML5 confuses matters.
My initial reactions to HTML5 help were good; it looked nice and I liked the new search results. After using it properly, and trying to design my own skin and stylesheet, I'm coming to the conclusion it was released too early as it seems to have a lot of bugs/niggles.
I know they need to differentiate it from WebHelp, but calling the target type HTML5 confuses matters.
My initial reactions to HTML5 help were good; it looked nice and I liked the new search results. After using it properly, and trying to design my own skin and stylesheet, I'm coming to the conclusion it was released too early as it seems to have a lot of bugs/niggles.
Re: Where's the HTML5 in HTML5 output?
Gary, be sure you also require that IE8 NOT be running your help in Compatibility View, which essentially turns IE8 into IE7. This setting won't even recognize many of the long-established CSS3 specifications that other browsers do, let alone the anticipated HTML5/WebHelp 2.0 features.
Good luck,
Leon
Good luck,
Leon
Re: Where's the HTML5 in HTML5 output?
Yeah, I agree. I don't believe in taking functionality away from end users unless it's replaced with something comparable or better, and the fact that search results don't highlight in HTML5 and the TOC doesn't sync breaks my rules, so I'm sticking with WebHelp output. I'm really really really hoping they'll fix some of the bugs in the HTML5 output and release a minor rev to v8 soon.Dave Lee wrote:My initial reactions to HTML5 help were good; it looked nice and I liked the new search results. After using it properly, and trying to design my own skin and stylesheet, I'm coming to the conclusion it was released too early as it seems to have a lot of bugs/niggles.
Lisa
Eagles may soar, but weasels aren't sucked into jet engines.
Warning! Loose nut behind the keyboard.
-
Robotman
- Sr. Propeller Head
- Posts: 186
- Joined: Sat Mar 04, 2006 3:05 am
- Location: Melbourne, Australia
- Contact:
Re: Where's the HTML5 in HTML5 output?
Thanks, Leon. I forgot about IE8s compatibility view (I'll add that to our testing). We haven't actually implemented it yet although we're close to doing so. I tested in IE6 and it was unusable; figured v7 would be the same.crdmerge wrote:Gary, be sure you also require that IE8 NOT be running your help in Compatibility View, which essentially turns IE8 into IE7. This setting won't even recognize many of the long-established CSS3 specifications that other browsers do, let alone the anticipated HTML5/WebHelp 2.0 features.