Sensor.frequency needs to be setable to allow frequency adaptation

[tobie]

Use case here is for example frequency of geo-location sensor for live positioning on a map which needs to be high when a map is zoomed in but can be much lower when the map is zoomed out.

More on this gist.

[anssiko]

Can this requirement be generalized to apply to any other properties?

[rwaldron]

This is definitely important and a hard lesson learned by Johnny-Five—which is currently in the planning process of migrating all sensor component classes to support changing frequency after a sensor instance object has been created.

[tobie]

Thanks for validating this with actual implementer feedback, @rwaldron.

[tobie]

As a sidenote, this probably should be a method returning a promise.

[alexshalamov]

@pozdnyakov This is same issue as #139 , I still think we should split parameters that are mutable during lifecycle of a sensor, frequency is one of such parameters.

[anssiko]

All - I'm hearing this issue should be after all deferred to Level 2. Please let us know if you think otherwise.

[anssiko]

I've heard no concerns since airing the proposal two week ago, so I have made a decision to defer this issue (back) to Level 2.

(We will likely revisit this issue when the Geolocation Sensor spec commences to this WG as proposed in the Charter draft. I opened a respective issue for the Geolocation Sensor spec https://github.com/WICG/geolocation-sensor/issues/16 to incubate the idea there meanwhile.)