This repository has been archived by the owner on Mar 1, 2024. It is now read-only.
Exposing the pixelstreaming interface to the browser. #420
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…omation to directly interact with the pixelstreaming features for testing etc.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Relevant components:
Problem statement:
Pixelstreaming is inaccessible to the browser and hidden away in the onload function. This prevents any ability for the browser to access the pixelstreaming interface for things like automated testing.
Solution
A global is now declared that can be accessed when using the browser context. This allows automation scripts to query information or even control the public interface of pixelstreaming.
Documentation
Test Plan and Compatibility