fix(navigator): check for experimental userAgentData first
#1548
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
✅ Deploy Preview for docsearch ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Comment on lines
+147
to
+148
| expect((navigator as any).userAgentData).not.be.undefined; | ||
| expect(navigator.platform).not.to.be.undefined; |
There was a problem hiding this comment.
This is testing the Chrome platform, not DocSearch. Why would we test this?
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.
Summary
https://algolia.atlassian.net/browse/CRAW-2433
Proposed in #1483 by @bershanskiy, moved here to add tests on top
This addition prevents the console warning when trying to detect the platform. We still fallback on the default navigator implementation if not found.