-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix AmbientLightSensor+Magnetometer API data #6699
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems blocked on #6509, or can we route around that issue somehow?
} | ||
], | ||
"chrome": { | ||
"version_added": "56" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately this will also run into #6509. 😢
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is fine to merge as it is before coming to a decision in #6509? This PR doesn't change the status of flag data inclusion in the subfeatures, which we'd need to check in every file with flags anyways.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, I guess so. This is a case that will be caught by any migration script, as the parent feature has flags but this does not.
This PR updates all of the data for the
AmbientLightSensor
API. When running results from the mdn-bcd-collector project, I noticed that it was reporting that the API was not supported in Chrome. Doing some digging around, it looks like the data was added very, very incorrectly.First off, the
AmbientLightSensor
API had always been based upon the Generic Sensor API since it was first implemented. Second, neither API was exposed by default -- the #enable-generic-sensor flag needed to be enabled (and then later, the #enable-generic-sensor-extra-classes as well).This data was determined by testing for
'AmbientLightSensor' in self;
and'Magnetometer' in self;
in BrowserStack in various Chrome versions with different flags.