Fixing the browser rendering issue for chrome and chromium browsers #3029
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
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.
... by modifying the "using" argument passed to open_html_in_browser method to be a tuple of strings.
This PR is to resolve this issue #2348.
File changes include
plotly.py/packages/python/plotly/plotly/io/_base_renderers.py
plotly.py/packages/python/plotly/plotly/io/_renderers.py
There would be no changes to documentation as the existing examples and tests would still apply, just the underlying implementation was changed to perform string matching.