Right now, DeviceAtlas doesn't have that sort of information available in it, but we're working hard on adding more data all the time.
In particular, CSS, JS & AJAX support is on our radar, and we're hoping to have some new properties relating to these added in the near future. Unfortunately, there are no hard dates set yet, but as soon as we have something exciting to say, you'll see it here on MobiForge.

Daniel

There is a stop-gap measure that can be used in the meanwhile, and that is to bolster the Device Atlas information with information found in WURFL.

That's what we've had to start doing, as we really needed the AJAX information that wasn't available in Device Atlas.

So, it does mean that we do two device lookups each time (but with caching enabled, this is no longer an issue), but it also means that we get the wealth of information available from two device databases.

You could perhaps look at implementing something like that?

Geoff,

I'd be very interested in learning more about your current setup. Do you find much latency in your approach? Is it reliable? Does WURFL provide different (either correct or incorrect) results for other information, in your experience?

Daniel