-
Notifications
You must be signed in to change notification settings - Fork 10.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor PDFFindController
to use the 'pagesinit' event, dispatched on the eventBus
, to resolve the _firstPagePromise
#9861
Merged
timvandermeij
merged 1 commit into
mozilla:master
from
Snuffleupagus:PDFFindController-firstPagePromise
Jul 2, 2018
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
… on the `eventBus`, to resolve the `_firstPagePromise` Rather than having to manually call a method on `PDFFindController` instances from `BaseViewer.setDocument`, thus essentially having to resolve the private `_firstPagePromise` from the "outside", this can be done easily with the 'pagesinit' event dispatched on the `eventBus` instead. Please note this particular `PDFFindController` code pre-dates the `eventBus` by almost three years, which should explain why the code looks the way it does.
/botio-windows preview |
From: Bot.io (Windows)ReceivedCommand cmd_preview from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.215.176.217:8877/f00c6e3456f1b66/output.txt |
From: Bot.io (Windows)SuccessFull output at http://54.215.176.217:8877/f00c6e3456f1b66/output.txt Total script time: 4.94 mins Published |
timvandermeij
approved these changes
Jul 2, 2018
Good idea to use the event bus here! |
movsb
pushed a commit
to movsb/pdf.js
that referenced
this pull request
Jul 14, 2018
…firstPagePromise Refactor `PDFFindController` to use the 'pagesinit' event, dispatched on the `eventBus`, to resolve the `_firstPagePromise`
This was referenced Mar 8, 2021
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.
Rather than having to manually call a method on
PDFFindController
instances fromBaseViewer.setDocument
, thus essentially having to resolve the private_firstPagePromise
from the "outside", this can be done easily with the 'pagesinit' event dispatched on theeventBus
instead.Please note this particular
PDFFindController
code pre-dates theeventBus
by almost three years, which should explain why the code looks the way it does.