Page MenuHomePhabricator

Not properly detecting Nintendo DS UA
Closed, ResolvedPublic

Description

This is going to be a tough one since it doesn't have anything mobile related in its UA

Mozilla/4.0 (compatible; MSIE 6.0; Nitro) Opera 8.50 [en Mozilla/4.0 (compatible; MSIE 6.0; Nitro) Opera 8.50 [ja]

Likely another case for css media queries.


Version: unspecified
Severity: normal

Details

Reference
bz30190

Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 11:49 PM
bzimport set Reference to bz30190.
bzimport added a subscriber: Unknown Object (MLST).

Go WURFL! This would solve our problem if squids could load the WURFL db directly. Since they can't and we have to use a limited set of ACL's to match a lot of UA's we have to be careful to not use too many.

If we have the breathing room then we might add this .. otherwise it'll be pending the Squid -> Varnish migration that ops is leading.

Isn't Nintendo DS just an opera browser? Thus can't we just detect it as opera? Is there any particular reason we need to detect it as a DS specifically?

According to http://www.mobile-phone-specs.com/model/nintendo_ds_ver1/ the default Nintendo DS UAs are:

Mozilla/4.0 (compatible; MSIE 6.0; Nitro) Opera 8.50 [en]
Opera/9.50 (Nintendo DSi; Opera/483; U; en-US)

Both of these UAs should be picked up by our device detection. It's likely this is no longer an issue. Can anyone confirm this?

Resolving. Will re-open if it shows up again.