Ever since 3.5, cross-domain HTTP requests have been supported in Firefox. Getting this to work may seem easier and saner than piggy-backing Flash ("simply request a URL of different origin in your
Ubiquity is a dynamic command and quasi-natural language add-on for Firefox, recently released by Mozilla Labs. It sure is getting ever so popular, so I decided to write two Drupal-related Ubiquity commands in one shot: drupal and drupal-api.
I promised to post the SunSpider benchmarks for Google Chrome, and boy, V8 surely blew away other browsers in many aspects! For the visual learners, here's a pretty chart to show just how monstrous Chrome is when it comes to JS perfs (as Intchanter noted, smaller is better):
Here are some nicely formatted raw numbers:
I have written two Ubiquity commands so far. If you have Ubiquity installed, you should be prompted to install commands when reading this page.
Drupal tools contains two commands, drupal and drupal-api.
drupal (node ID)
drupal opens the corresponding node on drupal.org.
drupal-api (function name) [on (drupal version)]
With the release of Google Chrome just coming up tomorrow, by now the blogosphere should be on fire with all the screenshots and juicy details. Even though I see Google Chrome as something that means more to the user than to the developer, there are certain goodies in Google Chrome that aim to provide a better platform for developers. What's the implication for web developers here?
One of my recent efforts is Prototype Essentials. It is, pardon my pun, essentially Prototype stripped of its browser-specific parts such as Ajax, DOM stuff, selectors, form helpers, and an event system. Why would anyone want a stripped down version of Prototype?
Array.last in Prototype), interpolate strings (
String.interpolate in Prototype), or construct ranges (
ObjectRange in Prototype). Now all I need to do now is load Prototype Essentials and I'd have a much richer set of utilities.
This is essentially a clean house implementation of the font detection method described at lalit dot lab using Prototype 1.6. Another method described at maratz.com seems very interesting, since it uses Flash.
This is only usable after the DOM is ready. Call
Font.detect with a string containing the name of the font to be detected. If it's detected as present,
true is returned, otherwise,
.constructor != new Array().constructor
It seems like this is a Firebug-specific issue. If you try to evaluate the above in Error Console, you'll get false.