- From: Sangwhan Moon <sangwhan@iki.fi>
- Date: Wed, 08 Oct 2014 12:33:06 +0900
- To: whatwg@lists.whatwg.org
Original Message: > On 24 Sep 2014 20:40, "James Graham" <james@hoppipolla.co.uk> wrote: > > > > On 24/09/14 02:54, Jonas Sicking wrote: > > > > > In the meantime, I'd like to add a property to window.navigator to > > > enable websites to get the same information from there as is already > > > available in the UA string. That would at least help with the parsing > > > problem. > > > > > > And if means that we could more quickly move the device model out of > > > the UA string, then it also helps with the UA-string keying thing. > > > > It's not entirely clear this won't just leave us with the device string > > in two places, and unable to remove either of them. Do we have any > > evidence that the sites using UA detection will all change their code in > > relatively short order, or become unimportant enough that we are able to > > break them? > > Why don't we provide a better structure and not just a random string. For > example: deviceID, browserID, renderingEngineVersion ... Not sure what > else > would be useful to group actions that the developer needs to take. > Haven't > looked in detail. On top of that, firmware version would be helpful, since most HWA/WebGL bugs are caused by driver bugs that directly relate to the firmware version. Sangwhan
Received on Wednesday, 8 October 2014 03:33:34 UTC