@marcoscaceres - https://github.com/w3c/geolocation-api/issues/15#issuecomment-631896781 -- GitHub Notification of comment by Ahmad-S792 Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/122#issuecomment-2005656841 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
anssiko has just submitted a new pull request for https://github.com/w3c/deviceorientation: == Add Accessibility considerations == This text is authored by APA WG and its APA consensus is recorded in: https://lists.w3.org/Archives/Public/public-apa-admin/2024Mar/0000.html See https://github.com/w3c/deviceorientation/pull/150 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
anssiko has just submitted a new pull request for https://github.com/w3c/deviceorientation: == Add Accessibility considerations == This text is authored by APA WG and its APA consensus is recorded in: https://lists.w3.org/Archives/Public/public-apa-admin/2024Mar/0000.html See https://github.com/w3c/deviceorientation/pull/150 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
anssiko has just submitted a new pull request for https://github.com/w3c/deviceorientation: == Add Accessibility considerations == This text is authored by APA WG and its APA consensus is recorded in: https://lists.w3.org/Archives/Public/public-apa-admin/2024Mar/0000.html See https://github.com/w3c/deviceorientation/pull/150 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
anssiko has just submitted a new pull request for https://github.com/w3c/deviceorientation: == Add Accessibility considerations == This text is authored by APA WG and its APA consensus is recorded in: https://lists.w3.org/Archives/Public/public-apa-admin/2024Mar/0000.html See https://github.com/w3c/deviceorientation/pull/150 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
himorin has just submitted a new pull request for https://github.com/w3c/geolocation-api: == Added webapps as group == Closes nothing The following tasks have been completed: n/a Implementation commitment: n/a /cc @marcoscaceres See https://github.com/w3c/geolocation-api/pull/144 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
himorin has just submitted a new pull request for https://github.com/w3c/geolocation-api: == Added webapps as group == Closes nothing The following tasks have been completed: n/a Implementation commitment: n/a /cc @marcoscaceres See https://github.com/w3c/geolocation-api/pull/144 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
rakuco has just submitted a new pull request for https://github.com/w3c/deviceorientation: == automation: Adapt to Generic Sensor changes to stash provided readings == Just like with w3c/sensor#487, the idea is to make it possible for users to write, for example ```js await test_driver.create_virtual_sensor(...); await test_driver.update_virtual_sensor(...); window.addEventListener('deviceorientation', ...); ``` and receive the readings above even if the connection to the virtual sensor was made only after the addEventListener() call. Previously, users would need to carefully order the calls to addEventListener(), update_virtual_sensor() and possibly even need to add a dummy event listener first to get everything to work correctly. Unfortunately, just as with w3c/sensor#487 this requires quite a few changes, even more so in this specification, which is quite vague when it comes to connecting to sensors and the lifetimes of such connections. Some of that behavior is now specified for the virtual sensors case, so that each Document has a `[[virtualSensorMapping]]` that maps virtual sensor types to "orientation event platform sensor-likes", a concept borrowed from Generic Sensor's automation section. Similarly to that section, the idea is that: - Whenever the user agent needs to connect to the underlying hardware because addEventListener() was called, it first attempts to find a virtual sensor, get/create an orientation event platform sensor-like, adds it to `[[virtualSensorMapping]]` and to the virtual sensor's connected platform sensors set and retrieves any existing readings from the virtual sensor. - When a Document is being unloaded, all platform sensor-likes in `[[virtualSensorMapping]]` are removed from their virtual sensors' connected platform sensors set. - Similarly, when a virtual sensor is removed, any platform sensor-likes in its connected platform set have their associated "device sensor" set to null. In the rest of the spec, we switch from attempting to derive a virtual sensor from the top-level traversable directly to trying to find a suitable platform sensor-like entry in `[[virtualSensorMapping]]` and checking its associated virtual sensor when one is set. Related to: w3c/sensors#478. See https://github.com/w3c/deviceorientation/pull/147 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
rakuco has just submitted a new pull request for https://github.com/w3c/deviceorientation: == automation: Adapt to Generic Sensor changes to stash provided readings == Just like with w3c/sensor#487, the idea is to make it possible for users to write, for example ```js await test_driver.create_virtual_sensor(...); await test_driver.update_virtual_sensor(...); window.addEventListener('deviceorientation', ...); ``` and receive the readings above even if the connection to the virtual sensor was made only after the addEventListener() call. Previously, users would need to carefully order the calls to addEventListener(), update_virtual_sensor() and possibly even need to add a dummy event listener first to get everything to work correctly. Unfortunately, just as with w3c/sensor#487 this requires quite a few changes, even more so in this specification, which is quite vague when it comes to connecting to sensors and the lifetimes of such connections. Some of that behavior is now specified for the virtual sensors case, so that each Document has a `[[virtualSensorMapping]]` that maps virtual sensor types to "orientation event platform sensor-likes", a concept borrowed from Generic Sensor's automation section. Similarly to that section, the idea is that: - Whenever the user agent needs to connect to the underlying hardware because addEventListener() was called, it first attempts to find a virtual sensor, get/create an orientation event platform sensor-like, adds it to `[[virtualSensorMapping]]` and to the virtual sensor's connected platform sensors set and retrieves any existing readings from the virtual sensor. - When a Document is being unloaded, all platform sensor-likes in `[[virtualSensorMapping]]` are removed from their virtual sensors' connected platform sensors set. - Similarly, when a virtual sensor is removed, any platform sensor-likes in its connected platform set have their associated "device sensor" set to null. In the rest of the spec, we switch from attempting to derive a virtual sensor from the top-level traversable directly to trying to find a suitable platform sensor-like entry in `[[virtualSensorMapping]]` and checking its associated virtual sensor when one is set. Related to: w3c/sensors#478. See https://github.com/w3c/deviceorientation/pull/147 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
rakuco has just submitted a new pull request for https://github.com/w3c/deviceorientation: == automation: Adapt to Generic Sensor changes to stash provided readings == Just like with w3c/sensor#487, the idea is to make it possible for users to write, for example ```js await test_driver.create_virtual_sensor(...); await test_driver.update_virtual_sensor(...); window.addEventListener('deviceorientation', ...); ``` and receive the readings above even if the connection to the virtual sensor was made only after the addEventListener() call. Previously, users would need to carefully order the calls to addEventListener(), update_virtual_sensor() and possibly even need to add a dummy event listener first to get everything to work correctly. Unfortunately, just as with w3c/sensor#487 this requires quite a few changes, even more so in this specification, which is quite vague when it comes to connecting to sensors and the lifetimes of such connections. Some of that behavior is now specified for the virtual sensors case, so that each Document has a `[[virtualSensorMapping]]` that maps virtual sensor types to "orientation event platform sensor-likes", a concept borrowed from Generic Sensor's automation section. Similarly to that section, the idea is that: - Whenever the user agent needs to connect to the underlying hardware because addEventListener() was called, it first attempts to find a virtual sensor, get/create an orientation event platform sensor-like, adds it to `[[virtualSensorMapping]]` and to the virtual sensor's connected platform sensors set and retrieves any existing readings from the virtual sensor. - When a Document is being unloaded, all platform sensor-likes in `[[virtualSensorMapping]]` are removed from their virtual sensors' connected platform sensors set. - Similarly, when a virtual sensor is removed, any platform sensor-likes in its connected platform set have their associated "device sensor" set to null. In the rest of the spec, we switch from attempting to derive a virtual sensor from the top-level traversable directly to trying to find a suitable platform sensor-like entry in `[[virtualSensorMapping]]` and checking its associated virtual sensor when one is set. Related to: w3c/sensors#478. See https://github.com/w3c/deviceorientation/pull/147 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
rakuco has just submitted a new pull request for https://github.com/w3c/deviceorientation: == automation: Adapt to Generic Sensor changes to stash provided readings == Just like with w3c/sensor#487, the idea is to make it possible for users to write, for example ```js await test_driver.create_virtual_sensor(...); await test_driver.update_virtual_sensor(...); window.addEventListener('deviceorientation', ...); ``` and receive the readings above even if the connection to the virtual sensor was made only after the addEventListener() call. Previously, users would need to carefully order the calls to addEventListener(), update_virtual_sensor() and possibly even need to add a dummy event listener first to get everything to work correctly. Unfortunately, just as with w3c/sensor#487 this requires quite a few changes, even more so in this specification, which is quite vague when it comes to connecting to sensors and the lifetimes of such connections. Some of that behavior is now specified for the virtual sensors case, so that each Document has a `[[virtualSensorMapping]]` that maps virtual sensor types to "orientation event platform sensor-likes", a concept borrowed from Generic Sensor's automation section. Similarly to that section, the idea is that: - Whenever the user agent needs to connect to the underlying hardware because addEventListener() was called, it first attempts to find a virtual sensor, get/create an orientation event platform sensor-like, adds it to `[[virtualSensorMapping]]` and to the virtual sensor's connected platform sensors set and retrieves any existing readings from the virtual sensor. - When a Document is being unloaded, all platform sensor-likes in `[[virtualSensorMapping]]` are removed from their virtual sensors' connected platform sensors set. - Similarly, when a virtual sensor is removed, any platform sensor-likes in its connected platform set have their associated "device sensor" set to null. In the rest of the spec, we switch from attempting to derive a virtual sensor from the top-level traversable directly to trying to find a suitable platform sensor-like entry in `[[virtualSensorMapping]]` and checking its associated virtual sensor when one is set. Related to: w3c/sensors#478. See https://github.com/w3c/deviceorientation/pull/147 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
rakuco has just submitted a new pull request for https://github.com/w3c/deviceorientation: == automation: Adapt to Generic Sensor changes to stash provided readings == Just like with w3c/sensor#487, the idea is to make it possible for users to write, for example ```js await test_driver.create_virtual_sensor(...); await test_driver.update_virtual_sensor(...); window.addEventListener('deviceorientation', ...); ``` and receive the readings above even if the connection to the virtual sensor was made only after the addEventListener() call. Previously, users would need to carefully order the calls to addEventListener(), update_virtual_sensor() and possibly even need to add a dummy event listener first to get everything to work correctly. Unfortunately, just as with w3c/sensor#487 this requires quite a few changes, even more so in this specification, which is quite vague when it comes to connecting to sensors and the lifetimes of such connections. Some of that behavior is now specified for the virtual sensors case, so that each Document has a `[[virtualSensorMapping]]` that maps virtual sensor types to "orientation event platform sensor-likes", a concept borrowed from Generic Sensor's automation section. Similarly to that section, the idea is that: - Whenever the user agent needs to connect to the underlying hardware because addEventListener() was called, it first attempts to find a virtual sensor, get/create an orientation event platform sensor-like, adds it to `[[virtualSensorMapping]]` and to the virtual sensor's connected platform sensors set and retrieves any existing readings from the virtual sensor. - When a Document is being unloaded, all platform sensor-likes in `[[virtualSensorMapping]]` are removed from their virtual sensors' connected platform sensors set. - Similarly, when a virtual sensor is removed, any platform sensor-likes in its connected platform set have their associated "device sensor" set to null. In the rest of the spec, we switch from attempting to derive a virtual sensor from the top-level traversable directly to trying to find a suitable platform sensor-like entry in `[[virtualSensorMapping]]` and checking its associated virtual sensor when one is set. Related to: w3c/sensors#478. See https://github.com/w3c/deviceorientation/pull/147 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
rakuco has just submitted a new pull request for https://github.com/w3c/deviceorientation: == automation: Adapt to Generic Sensor changes to stash provided readings == Just like with w3c/sensor#487, the idea is to make it possible for users to write, for example ```js await test_driver.create_virtual_sensor(...); await test_driver.update_virtual_sensor(...); window.addEventListener('deviceorientation', ...); ``` and receive the readings above even if the connection to the virtual sensor was made only after the addEventListener() call. Previously, users would need to carefully order the calls to addEventListener(), update_virtual_sensor() and possibly even need to add a dummy event listener first to get everything to work correctly. Unfortunately, just as with w3c/sensor#487 this requires quite a few changes, even more so in this specification, which is quite vague when it comes to connecting to sensors and the lifetimes of such connections. Some of that behavior is now specified for the virtual sensors case, so that each Document has a `[[virtualSensorMapping]]` that maps virtual sensor types to "orientation event platform sensor-likes", a concept borrowed from Generic Sensor's automation section. Similarly to that section, the idea is that: - Whenever the user agent needs to connect to the underlying hardware because addEventListener() was called, it first attempts to find a virtual sensor, get/create an orientation event platform sensor-like, adds it to `[[virtualSensorMapping]]` and to the virtual sensor's connected platform sensors set and retrieves any existing readings from the virtual sensor. - When a Document is being unloaded, all platform sensor-likes in `[[virtualSensorMapping]]` are removed from their virtual sensors' connected platform sensors set. - Similarly, when a virtual sensor is removed, any platform sensor-likes in its connected platform set have their associated "device sensor" set to null. In the rest of the spec, we switch from attempting to derive a virtual sensor from the top-level traversable directly to trying to find a suitable platform sensor-like entry in `[[virtualSensorMapping]]` and checking its associated virtual sensor when one is set. Related to: w3c/sensors#478. See https://github.com/w3c/deviceorientation/pull/147 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
marcoscaceres has just submitted a new pull request for https://github.com/w3c/deviceorientation: == chore: add Marcos to editorial team == Would like to join the Editorial team, as I'd like to make sure things align with WebKit. See https://github.com/w3c/deviceorientation/pull/146 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
marcoscaceres has just submitted a new pull request for https://github.com/w3c/geolocation-api: == chore: bring Marcos out of retirement == None See https://github.com/w3c/geolocation-api/pull/143 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
reillyeon has just created a new issue for https://github.com/w3c/deviceorientation: == "Status of this document" section needs to reflect join deliverable status == As discussed in https://github.com/w3c/deviceorientation/pull/142 the "Status of this document" section does not sufficiently reflect the joint deliverable status of this specification. That CL adds "text macro" declarations which should be sufficient but there appear to be deficiencies in the Bikeshed boilerplate text which need to be addressed. In particular, the line "This document was produced by the [Devices and Sensors Working Group](https://www.w3.org/groups/wg/das/)." should read something like "This document was produced as a joint deliverable of the [Devices and Sensors Working Group](https://www.w3.org/groups/wg/das/) and [Web Applications Working Group](https://www.w3.org/groups/wg/webapps/)." We also found that while there is a section on the W3C Patent Policy which acknowledges the joint deliverable status it would also be helpful for the document to also be explicit about the need to satisfy the success criteria for both groups. Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/145 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
reillyeon has just created a new issue for https://github.com/w3c/deviceorientation: == "Status of this document" section needs to reflect join deliverable status == As discussed in https://github.com/w3c/deviceorientation/pull/142 the "Status of this document" section does not sufficiently reflect the joint deliverable status of this specification. That CL adds "text macro" declarations which should be sufficient but there appear to be deficiencies in the Bikeshed boilerplate text which need to be addressed. In particular, the line "This document was produced by the [Devices and Sensors Working Group](https://www.w3.org/groups/wg/das/)." should read something like "This document was produced as a joint deliverable of the [Devices and Sensors Working Group](https://www.w3.org/groups/wg/das/) and [Web Applications Working Group](https://www.w3.org/groups/wg/webapps/)." We also found that while there is a section on the W3C Patent Policy which acknowledges the joint deliverable status it would also be helpful for the document to also be explicit about the need to satisfy the success criteria for both groups. Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/145 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
To be discussed with PING when a solution is identified, latest prior to the Proposed Rec transition. Context: https://github.com/w3cping/privacy-request/issues/128 -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/87#issuecomment-1985287520 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
To be discussed with PING when a solution is identified, latest prior to the Proposed Rec transition. Context: https://github.com/w3cping/privacy-request/issues/128 -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/87#issuecomment-1985287520 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
To be discussed with PING when a solution is identified, latest prior to the Proposed Rec transition. Context: https://github.com/w3cping/privacy-request/issues/128 -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/87#issuecomment-1985287520 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
To be discussed with PING when a solution is identified, latest prior to the Proposed Rec transition. Context: https://github.com/w3cping/privacy-request/issues/128 -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/87#issuecomment-1985287520 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
anssiko has just submitted a new pull request for https://github.com/w3c/deviceorientation: == Add an inline issue for the maximum sampling frequency cap == None See https://github.com/w3c/deviceorientation/pull/144 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
reillyeon has just submitted a new pull request for https://github.com/w3c/deviceorientation: == Create PULL_REQUEST_TEMPLATE.md == Specification pull requests should be either be editorial or have test coverage and multi-implementor consensus. See https://github.com/w3c/deviceorientation/pull/143 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
reillyeon has just submitted a new pull request for https://github.com/w3c/deviceorientation: == Create PULL_REQUEST_TEMPLATE.md == Specification pull requests should be either be editorial or have test coverage and multi-implementor consensus. See https://github.com/w3c/deviceorientation/pull/143 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
reillyeon has just submitted a new pull request for https://github.com/w3c/deviceorientation: == Create PULL_REQUEST_TEMPLATE.md == Specification pull requests should be either be editorial or have test coverage and multi-implementor consensus. See https://github.com/w3c/deviceorientation/pull/143 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
reillyeon has just submitted a new pull request for https://github.com/w3c/deviceorientation: == Create PULL_REQUEST_TEMPLATE.md == Specification pull requests should be either be editorial or have test coverage and multi-implementor consensus. See https://github.com/w3c/deviceorientation/pull/143 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
reillyeon has just submitted a new pull request for https://github.com/w3c/deviceorientation: == Create PULL_REQUEST_TEMPLATE.md == Specification pull requests should be either be editorial or have test coverage and multi-implementor consensus. See https://github.com/w3c/deviceorientation/pull/143 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Oh I see. I don't understand why it was decided to use nested data structures for this. They should just have been flattened (accelerationX, etc.), but that's too late now. -- GitHub Notification of comment by annevk Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/91#issuecomment-1973544487 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Oh I see. I don't understand why it was decided to use nested data structures for this. They should just have been flattened (accelerationX, etc.), but that's too late now. -- GitHub Notification of comment by annevk Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/91#issuecomment-1973544487 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Oh I see. I don't understand why it was decided to use nested data structures for this. They should just have been flattened (accelerationX, etc.), but that's too late now. -- GitHub Notification of comment by annevk Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/91#issuecomment-1973544487 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Oh I see. I don't understand why it was decided to use nested data structures for this. They should just have been flattened (accelerationX, etc.), but that's too late now. -- GitHub Notification of comment by annevk Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/91#issuecomment-1973544487 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Oh I see. I don't understand why it was decided to use nested data structures for this. They should just have been flattened (accelerationX, etc.), but that's too late now. -- GitHub Notification of comment by annevk Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/91#issuecomment-1973544487 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Oh I see. I don't understand why it was decided to use nested data structures for this. They should just have been flattened (accelerationX, etc.), but that's too late now. -- GitHub Notification of comment by annevk Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/91#issuecomment-1973544487 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
anssiko has just submitted a new pull request for https://github.com/w3c/deviceorientation: == Update status of this document == For CR publication purposes. See https://github.com/w3c/deviceorientation/pull/142 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
reillyeon has just submitted a new pull request for https://github.com/w3c/deviceorientation: == Make DeviceMotionEventInit members nullable with null default == This change reverts #55 and defines the default values of the DeviceMotionEventInit as null as I believe was the original intent of the definition before that change. Null DeviceMotionEvent attributes have semantic meaning (they declare that the host does not provide the given sensor) and so script should be able to initialize an event with its attributes set to null. Fixed #91. See https://github.com/w3c/deviceorientation/pull/141 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
reillyeon has just submitted a new pull request for https://github.com/w3c/deviceorientation: == Make DeviceMotionEventInit members nullable with null default == This change reverts #55 and defines the default values of the DeviceMotionEventInit as null as I believe was the original intent of the definition before that change. Null DeviceMotionEvent attributes have semantic meaning (they declare that the host does not provide the given sensor) and so script should be able to initialize an event with its attributes set to null. Fixed #91. See https://github.com/w3c/deviceorientation/pull/141 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
reillyeon has just submitted a new pull request for https://github.com/w3c/deviceorientation: == Make DeviceMotionEventInit members nullable with null default == This change reverts #55 and defines the default values of the DeviceMotionEventInit as null as I believe was the original intent of the definition before that change. Null DeviceMotionEvent attributes have semantic meaning (they declare that the host does not provide the given sensor) and so script should be able to initialize an event with its attributes set to null. Fixed #91. See https://github.com/w3c/deviceorientation/pull/141 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
reillyeon has just submitted a new pull request for https://github.com/w3c/deviceorientation: == Make DeviceMotionEventInit members nullable with null default == This change reverts #55 and defines the default values of the DeviceMotionEventInit as null as I believe was the original intent of the definition before that change. Null DeviceMotionEvent attributes have semantic meaning (they declare that the host does not provide the given sensor) and so script should be able to initialize an event with its attributes set to null. Fixed #91. See https://github.com/w3c/deviceorientation/pull/141 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
@marcoscaceres what's the frequency cap in WebKit? Discussed in https://www.w3.org/2024/02/12-dap-minutes.html#t06 -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/87#issuecomment-1963036688 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
@marcoscaceres what's the frequency cap in WebKit? Discussed in https://www.w3.org/2024/02/12-dap-minutes.html#t06 -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/87#issuecomment-1963036688 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Summoning @marcoscaceres Discussed in https://www.w3.org/2024/02/12-dap-minutes.html#t10 -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/137#issuecomment-1963034619 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Summoning @marcoscaceres Discussed in https://www.w3.org/2024/02/12-dap-minutes.html#t10 -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/137#issuecomment-1963034619 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Do we want to try address this by the upcoming CR Snapshot or defer for later? Works both ways. Discussed in https://www.w3.org/2024/02/12-dap-minutes.html#t10 -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/118#issuecomment-1963034094 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Closing per https://www.w3.org/2024/02/12-dap-minutes.html#t03 -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/30#issuecomment-1963032734 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
anssiko closed this issue. See https://github.com/w3c/deviceorientation/issues/30 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
anssiko closed this issue. See https://github.com/w3c/deviceorientation/issues/11 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config