Most browsers do not allow images to be cropped using CSS3’s border-radius. Tim Van Damme recently posted a workaround for this issue. Here’s a MooTools script that automates Tim’s workaround yet degrades gracefully when JavaScript is disabled.
Mozilla, the makers of Firefox, refuse to support the MP4/H.264 standard because it isn’t open-source and free from licensing constraints. Without Ogg, Firefox’s HTML5 video is rendered useless and requires a Flash-based fallback system. However, Firefox’s handling of the video element breaks the fallback mechanism. A scripted solution is required.
Here’s a simple script that will detect whether HTML 5 video is supported in the browser, and if it is, will check to see if this is Firefox. If yes, it deletes the specified video element but leaves the Flash fallback in its place.
MooTools’ removeClass utility will only work if the classes you want to remove are listed in the same order as the target element’s className property. Here’s a new removeClasses utility that fixes this shortcoming. A framework-neutral version is also provided.
I’m currently working on a new quiz system at work, and decided I’d incorporate Filament’s wonderful stylized checkboxes and radio buttons into my project, which meant it was time to roll up my sleeves and code me some Moo.
I’m happy to introduce you to my latest project, LearnSWFObject.com
I’m curious about what people are looking for in their e-learning authoring tools.
It took me much much longer than I anticipated, but I am happy to announce the new CaptivateController utility.
This controller is not a simple rehash of the original pipwerks.captivate.control utility; it is a complete re-write that adds a number of extra features.
The folks at Adobe recently published a list of Captivate 4 variables. While it’s a solid list, it’s not really a complete list.
I’ve had a flurry of emails and messages regarding my SCORM cheat the past few days, and have received feedback from a number of well-regarded SCORM aficionados, some of whom contributed to the standard and helped make SCORM what it is today. This is wonderful, I’m very happy to hear from everyone, especially regarding such an engaging topic.
But as I hear more from these seasoned SCORM pros, I’ve made (what I believe to be) an interesting observation: there is a sharp division between die-hard SCORM developers and casual users. I suppose I’ve felt this way for a long time, but it’s really coming into focus this week. Let me try to define the camps.
Internet Explorer 8 (IE8) is at Release Candidate 1, which means it will be released very shortly. IE8 is a brand-new browser and will represent a considerable shift from IE7/IE6; it will follow standards more closely and will offer much improved CSS 2.1 support. However, because of some of these changes, it is also widely understood that IE8 might ‘break’ websites that have relied on IE-specific hacks targeted at previous versions if Internet Explorer.
