Step 2 validates the track. Step 4.2 validates the token. The validation of the token is asynchronous. There are multiple reasons, but the simplest one is that if the token originates from a cross-origin iframe (which is also out-of-process), that iframe could be navigated, leading to all of its tokens becoming invalidated. To validate the token's validity, communication with another process is necessary, be it a central coordinating process (Chrome's current implementation) or the iframe's process (theoretically speaking). -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/14#issuecomment-1026182173 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Monday, 31 January 2022 20:31:51 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:55 UTC