- From: Johanna <notifications@github.com>
- Date: Tue, 22 Jan 2019 11:49:40 +0000 (UTC)
- To: w3c/screen-orientation <screen-orientation@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/screen-orientation/issues/136@github.com>
Currently in the spec we have: > <p> > The following is used but not defined in [[FULLSCREEN]]: <dfn><a href= > 'https://github.com/whatwg/fullscreen/issues/16'>animation frame > task</a></dfn>. > </p> According to the fullscreen issue referenced above the timing is now defined and the issue has been closed. @foolip Would you please be able to clarify what this means for the definition in the Screen Orientation spec and also where animation frame task appears in the algorithms: > <p>If locking the orientation did not result in a change of > orientation, as part of the next <a>animation frame task</a>, resolve > <var>pending-promise</var> with <code>undefined</code> and set <var> > pending-promise</var> to <code>null</code>. > </p> > <p> > Whenever the viewport's angle changes, the <a>user agent</a> MUST run > the following steps as part of the next <a>animation frame task</a>: > </p> > <p> > Whenever a <a>document</a> becomes visible per [[!PAGE-VISIBILITY]], > in other words after the <a>now visible algorithm</a> is run, the > <a>user agent</a> MUST run the following substeps as part of the next > <a>animation frame task</a>: > </p> Thank you very much for your help 🙂 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/screen-orientation/issues/136
Received on Tuesday, 22 January 2019 11:50:33 UTC