The original main goal was to give a name to the existing algorithm that
used to run in the "next animation frame task" so that it could be
referenced in the upcoming WebDriver section, but "animation frame task" as
a concept did not exist, and one thing led to another and the final change
includes a better version of the original algorithms, but without any
user-visible changes.
This change borrows a lot of ideas from the Screen Orientation spec as of
its 2023-08-09 Editor's Draft.
Most important changes:
The "update the device posture information" algorithm was renamed to
"calculate the device posture information" so that it returns a value
instead of updating [[CurrentPosture]] directly -- that is done as task
queued in the user interaction task source (more on this below).
Call the main algorithm "device posture change steps".
Merge the separate page visibility-related algorithm into the main one,
and add the proper checks to it to ensure that documents whose visibility
state is "hidden" are not updated and that calls to "update the device
posture information" that result in the same value being stored do not
fire any "change" events.
The "change" event is now queued to be fired in the user interaction task
source so that the moment it is actually fired is more predictable (the
"device posture change steps" are not running at any specific point of the
HTML event loop).
While here: the definition of the onchange attribute was updated to
mention the current terms defined in the HTML spec, along with a proper
<dfn> for the event handler event type.
The language and the references used in the text have also been updated: we
no longer deal with browsing contexts, but with navigables; the
PAGE-VISIBILITY spec is no longer treated as a separate specification, as it
was merged into HTML a few years ago.
The original main goal was to give a name to the existing algorithm that used to run in the "next animation frame task" so that it could be referenced in the upcoming WebDriver section, but "animation frame task" as a concept did not exist, and one thing led to another and the final change includes a better version of the original algorithms, but without any user-visible changes.
This change borrows a lot of ideas from the Screen Orientation spec as of its 2023-08-09 Editor's Draft.
Most important changes:
[[CurrentPosture]]directly -- that is done as task queued in the user interaction task source (more on this below).While here: the definition of the
onchangeattribute was updated to mention the current terms defined in the HTML spec, along with a proper<dfn>for the event handler event type.The language and the references used in the text have also been updated: we no longer deal with browsing contexts, but with navigables; the PAGE-VISIBILITY spec is no longer treated as a separate specification, as it was merged into HTML a few years ago.
Related to #104. Fixes #95.
Preview | Diff