5 Nov 2010 8:28 PM #1
How to control what non-webkit browsers "see"
Just curious...for those browsers that don't support webkit (Firefox, for example) is there a way to control the image that the user sees? I did a quick animation, tested it in Firefox, and the image I see looks all garbled and nasty. Is there any way to specify that some sort of static image is shown to browsers that don't support this animation? I'd like for people to see something at least somewhat nice (even if it's static) instead of gobbledy gook.
I hope that makes sense.
Thanks! Btw, this application is seriously awesome. I've been looking for a non-flash app to do an animation lead-in for my business site for ages, and I'm really excited to have stumbled upon this one.
8 Nov 2010 8:22 AM #2
I'm having the same issue with firefox and IE, is there anything we can do other than filtering users in our websites?
9 Nov 2010 11:25 AM #3
The easist thing to do is to position a full width/height div/image smack on top of everything and then add an initial keyframe that moves it off stage. Non-webkit browsers will ignore the animation and you'll get your fallback image.
The proper, but vastly more time-consuming way to do it is to create a somewhat meaningful scrollable layout of your images and text, then use initial keyframes to move everything off page, and bring them into the stage from there.
9 Nov 2010 4:34 PM #4
Thank you! The first part I get....it's this second bit that I'm not quite following: "create a somewhat meaningful scrollable layout of your images and text" What do you mean by somewhat meaningful scrollable layout??? Thanks again for your help - I really appreciate it. Cheers, -Kristine
13 Nov 2010 6:14 PM #5
What I mean is that you could actually layout the content of your animation in an overflow=auto stage - images, captions etc, in an order that makes sense. You could create initial keyframes that move all this content off stage before you start to animate it. In this way, older browsers will get an experience that isn't animated, but still shows the content, while new browsers get the animation. It involves some manual hacking of the output HTML/CSS, but it gets you there.
By timcharnecki in forum Ext 3.x: BugsReplies: 0Last Post: 23 Sep 2010, 12:10 PM
By GirijaSubramanian in forum Sencha Touch 1.x: DiscussionReplies: 2Last Post: 2 Aug 2010, 1:12 PM
By rblon in forum Ext 3.x: Help & DiscussionReplies: 2Last Post: 27 Jul 2010, 8:57 PM
By amlody in forum Ext 3.x: BugsReplies: 4Last Post: 17 Mar 2010, 5:46 AM