I’ve now added the code that Hype support sent me to all pages, but also redone the ‘Who We Are’ pages animation using gifs for the lettering rather than pngs (which I read somewhere didn’t get on with Internet Explorer very well) so fingers crossed and we’ll see how today goes!
I’m still inclined to think they won’t see it and it’s a pc specific issue, but here goes…
On 8 Jul 2013, at 23:11, DeltaDave wrote:
He”s on Windows 7, IE 10.
Looks fine with that too.
Always tricky when it comes down to Box specific issues.
Add the Code and try again but this may not be something that you can ‘fix’ if it is a particular setting on their PCs
I’m trying to learn Hype at the moment and seem to remember reading somewhere on Hype’s site about using PNGs with transparency - I believe they recommended using Gifs with transparency otherwise there may be issues with viewing movies on certain PCs.
Of course the above may be complete rubbish and I was dreaming, if so ignore me
Hi Neil, thanks for that, that’s what I read also. I redid one of the 3 movies using gifs, put the code Hype supplied into the master page (which did all of the children) and I’ve just heard back that the client can see everything.
So the answer was the code which apparently Freeway should be doing, and as an aside, the 2 movies using pngs work fine and there’s no difference between the quality of these and the gif movie.
All happy now, and thanks to everyone for the help.
I added the code for the movie manually into the area on the page where it was needed, and this displayed fine on virtually everything tested.
Hype support told me that Freeway should have set the head tags and added the
code automatically on publish, so that was the problem with it not being seen on certain setups. So we’re talking 2 separate sets of code here, the animation code (input by me) and the Head tag code above (not set by Freeway and the added by me).
But can anyone explain to me what the above actually means (X-UA-Compatible, Chromw=1, IE=Edge)?
You misunderstand David, it’s not my assumption, it’s Tumult Hype.
They say the code for the movie should have been added by me (which it was) and then they reckon it should have ‘triggered’ FW to write the head code somehow. This now gets beyond my little brain on how things work, so all I know is that I’m happy it’s working, and I have a fix for the future.
On 10 Jul 2013, at 23:02, DeltaDave wrote:
Hype support told me that Freeway should have set the head tags and added the code automatically on publish.
I am just not sure why you think that FW should have added that code automatically.
Anything that you add as Markup is unknown to FW and it cannot react to it.
However there is an argument that FW should provide an option for setting it as an option in the Page Compatibility section of the Inspector.
my Hype Action now adds this meta tag to the head tag in Freeway:
The other one they recommend is already added by Freeway to the mix. It’s worth pointing out that Hype outputs UTF-8, so if you set Freeway to do that, then the correct meta tag for that should be output automagically.