Posted by garbetjie 1 year 49 weeks ago
Hey all.
Does anyone know how often device properties in Device Atlas are updated? As an example, we're looking for the scriptSupport property availability for the Apple iPhone.
However, there is no data available for the iPhone and it's scriptSupport property yet. I've just taken a look at the WURFL data for the iPhone, and according to it, Javascript (AJAX in particular) is supported.
<group id="ajax"> <capability name="ajax_xhr_type" value="standard"/> <capability name="ajax_support_getelementbyid" value="true"/> <capability name="ajax_support_event_listener" value="true"/> <capability name="ajax_manipulate_dom" value="true"/> <capability name="ajax_support_javascript" value="true"/> <capability name="ajax_support_inner_html" value="true"/> <capability name="ajax_manipulate_css" value="true"/> <capability name="ajax_support_events" value="true"/> </group>
So how long would it take for this data to be pulled in to Device Atlas?
I hope I've made the question as clear as mud ;)




Posted by daniel.hunt 1 year ago
Mobile Grandmaster
Basically, DA is updated "when we get new data".
We get data from a number of sources, including WURFL, Nokia, our community of users and plenty more.
The "scriptSupport" property is, more or less, unused at the moment, and was intended to be a property-bag, which would list all of the types of scripts supported.
Unfortunately, saying that something "supports javascript" is simply not correct - there are a crazy number of combinations that could prove that it does actually do what it says on the tin.
We're looking into a number of new properties that relate specifically to HTML5 and JS at the moment, and would appreciate your input on my blog post if you have a few minutes.
Cheers,
Daniel HuntDaniel
dotMobi
Posted by garbetjie 1 year ago
Thanks for the response, Dan.
Is there any sort of time-line for these properties (at least, one that you know of)?
Doesn't WURFL already provide a suitable property bag though? As you can see from the example provided above, it already pulls out the individual JavaScript "parts" (for want of a better word) supported. Would it not be a case of emulating that bag within DA?
I've just commented on your blog post, with a similar suggestion :)