• Affected version: Firefox 51.0a1 (2016-09-14)

While the RDM tool is enabled, select LG G Watch device and check the User Agent in Network Monitor.

ER:

• The device related user agent is displayed.

AR:

• Firefox default user agent is displayed.

Logged based on https://bugzilla.mozilla.org/show_bug.cgi?id=1254386#c36

Note that the issue is also reproducible when selecting LG watch R, or Samsung Gear Live devices.

Being able to check the device's actual max touch points value via navigator.maxTouchPoints would be nice to have.

In Firefox DevTools' RDM tool, it's very difficult (if not impossible) to know what the simulated touch device's actual max touchpoints value is. While we could fake the value to be 1 for all touch devices, it would provide an inaccurate experience. For now, this issue could assume that all touches have max touchpoints of at least one.

See issue at: https://bugzilla.mozilla.org/show_bug.cgi?id=1500672

In #28 a lot of old devices got removed, leaving mostly high-end ones enabled. What is the reasoning¹ behind removing those devices?

I can only speak for myself, but I need to test the sites I'm developing on older devices, with a bad connection. Responsive design mode helps tremendously with that, I love it. I just wish it had more devices to choose from :)

Can these be brought back? Maybe behind a flag in about:config if nothing else.

I also wonder if Mozilla can pull some statistics for devices, and/or screens in use? Really it's the latter I'm mostly interested in as that's what I'll target using a @media query.

¹ I couldn't figure out why, as the PR didn't have a description and the commit message is just Update device list.

The cdn is giving an https error (certificate expired):
https://code.cdn.mozilla.net/devices/devices.json

code.cdn.mozilla.net uses an invalid security certificate.
The certificate expired on 16-03-2017 12:00.
The current time is 16-03-2017 14:34.
Error code: SEC_ERROR_EXPIRED_CERTIFICATE

We're opening this issue because your project has used Travis CI within the last 6 months. If you have already migrated off it, you can close and ignore this issue.

Travis CI is ending free builds on public repositories. travis-ci.com stopped providingthem in early November, and travis-ci.org will stop after December 31, 2020. To avoid disruptions to your workflows, you must migrate to another CI service.

For production use cases, we recommend switching to CircleCI. This service is already widely used within Mozilla. There is a guide to migrating from Travis CI to CircleCI available here.

For non production use cases, we recommend either CircleCI or Github Actions. There is a guide to migrating from Travis CI to Github Actions available here. Github Actions usage within Mozilla is new, and you will have to work with our github administrators to enable specific actions following this process.

If you have any questions, reach out in #github-admin:mozilla.org on matrix.

The list is missing the Samsung Galaxy S7 and Galaxy S8 profiles.

In addition - this hardcoded approach to the list is missing the option to re-order the devices by personal preference, but that's a more general firefox issue.

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please see Mozilla-GitHub-Standards or email [email protected].

(Message COC001)

We should describe what the featured attribute means in the README to help people making PRs.

Coming out of #22 (comment)

@clarkbw recently introduced the Samsung Galaxy S5 and S6 devices, but mentioned in #9 that their user agent strings were likely wrong.

We should fix them.

Firefox 63: I'm quite confused about why "Laptop with HiDPI screen" defaults to 900x1440 and I have to manually rotate it to 1440x900 every time. Same for "MDPI".

Did I miss people now using laptops in portrait, or what exactly is the rationale with such defaults?

(I'm also struggling to figure out why FF RDM defaults to 320x480, a preset that isn't even listed in the devices catalogue, and you can't change the default in any apparent way, but that's probably bugzilla material.) https://bugzilla.mozilla.org/show_bug.cgi?id=1443345

The list was last updated 2 years ago and even then it wasn't up to date.
(this is not criticism, I'm just asking around whether someone has a newer devices file)

Not sure where to send this one, figured it would make sense to ask here -

I have a bunch of Lenovo TAB2 A10-30 that I test things on. I thought it would be handy for them to be in the official list.

"name": "Lenovo TAB2 A10-30",
"width": 800,
"height": 1280,
"pixelRatio": 1,
"userAgent": "Mozilla/5.0 (Android 5.1.1; Tablet; rv:57.0) Gecko/57.0 Firefox/57.0",
"touch": true,
"firefoxOS": true,
"os": "android"

Thought I'd check. :)

We should probably get the Apple watch into our list of watches.

The list seems rather out of date. Some popular phones not listed:

• Google Pixel 2
• Google Pixel 2 XL
• Huawei Mate 10 Pro
• iPhone X
• iPhone 8
• iPhone 8 Plus
• OnePlus 5
• OnePlus 5T
• Samsung Galaxy S9
• Samsung Galaxy S9 Plus
• Samsung Galaxy Note 8

Additionally, the inclusion of unsupported and uncommon devices like Google Nexus phones seems strange at this point.