Several commenters have pointed out that @importRule would not be that useful since you can already assign more than one CSS class to an element.

However, having (apparently) some time to waste this morning, I thought it would be interesting to implement this pseudo css rule anyway.

Here’s the example page, with a short explanation of the (very simplistic) javascript:

Again, I’m not claiming that this is very useful, but if one wanted to create a javascript css post-processor, that would be a good way to start.

After months of work, the new FormAssembly.com is nearing completion.

This new version is a complete re-write, and since it is hosted on a completely separate platform, we are looking forward to a very smooth transition, with the two versions running concurrently for as long as necessary.

The feedback from the early beta-testers is pretty good. There are also plenty of new (and long requested) features, so I’m confident that our users will be happy with the new version.

I will also look at the traffic and conversion numbers attentively anxiously. In theory, the new site should perform much better, but sometimes what sells is really not what you think, so it will be interesting to compare the numbers. I’ll try to post my findings here.

A simple demonstration is available here, with all the explanations here.

Version 2.1 includes bug fixes and performance improvements. The major changes are:

• Upgraded to latest version of Sarissa (0.9.7.6)
• XSL stylesheet should now set the XSL:output method to “HTML”. This prevents an unnecessary HTML serialization & parsing step and avoids invalid HTML markup altogether, like self-closing <textarea/>. While this change makes 2.1 not backward compatible, this should be the only required change if you are using Freja 2.0.

I also updated the documentation and tutorials, which were beginning to be seriously out-of-date.

The Freja core development team is comprised of Cedric Savarese and Troels Knak-Nielsen. Freja is an Open-Source framework built on top of the Sarissa library by Manos Batsis.

This is still very experimental, but as you can see in the article, there are some clear benefits in terms of accessibility and speed when using XUL for complex UI widgets.

Check out the documentation and source for this experimental library and thanks to all for the feedback.

This time, I was thinking about the interface for the next version of the Form Builder (I know, somehow it’s always work related) and I was wondering if XUL could be of any help here.

A couple days later, I had this working: tabbed panel example.

If you are not using the Firefox browser, you will not see anything interesting, so here’s a screenshot of the second panel, viewed in Firefox (XUL powered).

The first panel in the example uses HTML+Javascript (a.k.a DHTML). It is very basic, there are better DHTML panel widgets of course. The idea is that you could enhance an existing javascript UI library to render widgets with XUL on XUL-compatible browsers…

You can check out the source code if you want to see how it’s done.

Update: As whoughton pointed out, it doesn’t degrades to DHTML as it should in Safari. I will fix that soon, it’s probably not a serious bug.

Update 2: The problem in Safari is caused by its user-agent. To detect whether I should render with XUL or DHTML, I look at the user-agent string. If it contains the word “gecko”, I assume the browser uses the Gecko rendering engine and therefore supports XUL… Well it turns out Safari’s user-agent string includes “Gecko” even though it’s not based on Gecko at all. Weird. Anyway, I’ll just have to fix the detection code.

Update 3. It’s fixed in Safari, thanks to Boris tips.