googlearchive / devtools-device-data

DevTools Device Mode Data

Please see the DevTools Frontend repository for the latest device data distributed with Chrome. This repository is no longer being updated.

This repository holds all of the device information that is provided to Chrome DevTools' device mode.

devtools-device-data's Issues

Add GoogleBot UAs

use case:
https://productforums.google.com/forum/#!category-topic/webmasters/mobile/xeViVssd5dQ

https://www.google.com/webmasters/tools/mobile-friendly/ uses those UAs and some UA sniffs treat the bots differently.

Need both Googlebot and Googlebot Mobile UAs.

Update contributing.md

With the pull of jsonschema validation the contributing guide needs a slight update.

I'll work on this at some point today or tomorrow.

Validate using JSON Schema

http://json-schema.org/examples.html
https://pypi.python.org/pypi/jsonschema

Should do this in the generate_ py script

Add Nexus 6 and 9

Device information should be added for the latest of the Nexus family.

I can add this myself once I get some time to get a UA string from the actual devices I can get a hold of. But if someone else can get in faster then that's fine too.

Nokia [Microsoft] Lumia Emulator Support

Hi, Chrome Emulation models does not including, most if not all the Nokia/Microsoft Lumia Phones, including what I own, the 1520. I'm in desperate need of this for the past week. I noticed some Lumia are listed, although some are missing particularly the 1520 or 1030 !

Include some of the top ChromeOS devices with screens.

Might be useful to see if some sales data could be gotten within Google to figure out the top say 4 ChromeOS laptops sold in the past few years. Add specs for those + the Pixel to the devices list. This would help developers targeting those. Of course this would need to be things like laptops and the LG all-in-one device. The simple boxes where you BYOM aren't useful since they inherently don't have set screen specs or input modes.

Help maintaining UAs

It's easy for these UAs to fall out of date.

We need an improved method of keeping these updated.

We want the UAs to represent the latest stable version of Chrome & Safari on each device.

Any suggestions?

Nexus 5X and 6P dimensions are incorrect

The Nexus 5X and 6P dimensions appear to be incorrect, as well as the device pixel ratio for the 6P. They should be the following:

Nexus 5X: 412x732
Nexus 6P: 412x732 with a DPR of 3.5

Microsoft Lumia 550 vertical screen not rotated

It is not rotated:

"type": "emulated-device",
        "device": {
            "show-by-default": false,
            "title": "Microsoft Lumia 550",
            "screen": {
                "horizontal": {
                    "width": 640,
                    "height": 360
                },
                "device-pixel-ratio": 2,
                "vertical": {
                    "width": 640,
                    "height": 360
                }
            },

Why desktop and notebook for accepted types?

Desktop and Notebook classifications are pretty much the exact same, except one is portable and the other is not. Couldn't we condense these two into one type?

Ref: https://github.com/GoogleChrome/devtools-device-data/blob/master/device_schema.json#L80

Keeping UA strings more automatically updated.

The UA string templates are already provided. What we could do is create a template string that for currently updated devices we automatically insert the latest variables. Then once a device is no longer supported we just hard-code the last known good UA string. This would only require us to keep one JSON template updated with the latest variables when new releases happen.

Any better thoughts? Some reason this isn't a good idea?

Some userAgents out of date

We have a few UAs out of date or missing.

• https://code.google.com/p/chromium/issues/detail?id=315607
• https://code.google.com/p/chromium/issues/detail?id=419365
• https://code.google.com/p/chromium/issues/detail?id=424185
• https://code.google.com/p/chromium/issues/detail?id=444152

Pull requests very welcome for this.

Import UA additions from upstream

In https://codereview.chromium.org/937303004/ I made a few changes

• dropped old and dead devices
• added new popular ones
• renamed a few things

sources:

• https://mixpanel.com/trends/#report/top_tablets
• http://bjango.com/articles/min-device-pixel-ratio/
• google

Need to update some things over here to match.

https://codereview.chromium.org/940193002/ updated some chrome UAs

Should we be tracking devices.json?

The devices.json is the output of generation. If this is tracked (as it currently is) then pulling in multiple merges quickly becomes a pain since each PR is going to conflict with that generated file.

Perhaps a better setup would be:

• Add devices.json to gitignore.
• Pre-commit hook that does validation of all the JSON files (taking advantage of what is being discussed in issue #9)
• If we could do a post-merge/push hook to auto-generate the devices.json that would be nice. Falling short of that just have it has a part of the build process for the DevTools.

Any other ideas?

Support for 'TV' devices

I suggest to add more classes of devices, like TV devices, so we should have

type = phone | tablet | notebook | desktop | tv | unknown