Update README (Chrome & Opera section) #6089
Merged
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
The Chrome extension is stable and has been around for a few years, so the ancient note about the extension being experimental can be removed. Also be a bit more specific about who maintains the Chrome extension, to make it easier for external contributors to find who is responsible for the development and maintenance of the PDF.js Chrome extension.
|
I'm good with the change. @brendandahl ? |
yurydelendik
added a commit
that referenced
this pull request
Jun 9, 2015
Update README (Chrome & Opera section)
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.
The Chrome extension is stable and has been around for a few years, so the ancient note about the extension being experimental can be removed.
Also be a bit more specific about who maintains the Chrome extension, to make it easier for external contributors to find who is responsible for the development and maintenance of the PDF.js Chrome extension (and who to
blamecontact when a release goes wrong).