Use DOM if possible and disable FPS flag - no longer needed #784
Conversation
This file contains hidden or 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
konraddysput
requested review from
paweltomaszewskisaucelabs and
FriggaHel
and removed request for
paweltomaszewskisaucelabs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
One-line summary
Adjust examples to our recent updates.
Description
The pull request shows how to use our basic features. During our meetings with customers, we have a lot of questions about FPS and DOM support. With the FPS and DOM support we should be sure our examples shows how to use it.
Types of Changes
What types of changes does your code introduce? Keep the ones that apply:
[x] New feature (non-breaking change which adds functionality)
[] Bug fix (non-breaking change which fixes an issue)
[] Configuration change
[] Refactor/improvements
[x] Documentation / non-code