Transform, Scale, Zoom, and more: across browsers

mag-inIn the process of creating an internal tool for my team I found that trying to zoom an image and move it around was not as simply as a single “zoom” CSS attribute. While Chrome supports “zoom” and it works quite well, the other browsers don’t work consistently, especially if you store the zoom and position values in a script. I stored the positions on the images to be replayed and I found all kinds of inconsistencies across browsers.  What did work consistently is the  transform CSS property, but that brought another challenge.

Continue reading

Advertisements

HTML5 Automation best in Internet Explorer – See for yourself

The video in the previous post did not do the test justice as many could not tell it truly is a smoother animation so here you go, you can view this web page yourself on the different browsers.

What I see on my machine is a much smoother animation of both the outer box and the growing text. Notice it is not choppy at all in IE, very smooth. And just an FYI, I am a solid Chrome user for a few years now, before that FireFox, and before that IE. With all of these IE commercials on television I had to see if this really was “faster”, at least in this space. I would be interested to hear what others see.

Link also here.

Internet Explorer KILLS the competition with HTML 5 Animation

I downloaded the Adobe’s new Edge Animate and played around with the tutorials for a bit and even did a basic animation. After I saved the HTML I then launched it into my default browser (Chrome) and was not very impressed. The animation was very choppy and even left blit marks throughout the animation, some really bad double buffering going on…

I then went back into Edge Animate and added even more animation, the text growing over the time line. This made it even worse in Chrome! I then opened the file in all of the major browsers (IE, FireFox, and Safari) and was amazed how great Internet Explorer did! It was by far the smoothest animation, with FireFox coming in a close second. You can’t completely tell by the video but you can definitely see how horrible Chrome is. And yes, these are all the latest browsers, except FireFox (I can’t keep up with their weekly updates).

I know this is a basic test but its pretty clear who the winner is here, without any “special” HTML5 code. It could also be that Adobe is in Microsofts pockets and intentionally made it perform better in IE but someone would have to prove that to me.

In the video I show Chrome, Safari, FireFox, then Internet Explorer.

All software should implement CTRL+ and CTRL-

I must be a FireFox advocate or at least like the zoom in and out shortcuts because I find myself using CTRL+/- in many places like Notes, Symphony, etc.  The only problem is the keys do nothing in them!

Who is with me?

Browser sniffing – Detecting what browser is being used with Dojo

Even though Dojo does a great job in making cross browser and platform JavaScript development very easy there are times when you may want to do something that is specific for a browser.  Instead of re-inventing the wheel you can use the many functions in the Dojo library to help with this. There is an entire article on “browser sniffing” on the Dojo toolkit web site and it comes with a few good examples to learn from:

  • dojo.isIE
  • dojo.isMozilla
  • dojo.isFF
  • dojo.isOpera
  • dojo.isSafari
  • dojo.isKhtml
  • dojo.isAIR – true if running within the Adobe AIR enviroment
  • dojo.isQuirks – is the browser in Quirks-Mode
  • dojo.isBrowser (not typically needed when only targeting browsers)