You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we still need to improve how the framework processes implementation info. "N/A" is being used to mean:
"Unknown": we don't have any info
"Not applicable": the spec is not meant to be implemented directly, e.g. a Note, or a best practices doc.
"Not supported". We know that the spec is not implemented in a user-agent.
The framework does not distinguish between these meanings at all. It actually does not even store the "Not supported" information that it gets from web platform sources for now.
In the case of the Generic Sensors spec, we don't have any info because status platforms do not report on that spec, but rather provide (sometimes incorrect - as reported in #160) info about concrete sensor specs.
We may hardcode some implementation info in the data file that describes Generic Sensor. Now, I confess I'm not entirely sure that info is really meaningul in practice: implementing the Generic Sensors spec per se does not mean much in isolation. It might be better to report something like "See more concrete sensor specs".
What would you rather see in the "Current implementation" column, @kenchris ?
So Generic Sensors spec is thus also in development
The text was updated successfully, but these errors were encountered: