#3200: run brick in top frame of window #3201
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
fregante
approved these changes
Apr 19, 2022
Comment on lines
+124
to
+127
| const sourceTabId = this.trace[0].tab.id; | ||
|
|
||
| const subRequest = { ...request, sourceTabId }; | ||
| return safelyRunBrick({ tabId: sourceTabId }, subRequest); |
There was a problem hiding this comment.
Looks about right. I left some notes on a possible messenger implementation:
This would let content scripts call this directly:
runBrick({ tabId: "this" }, request)and the messenger would take care of the forwarding. safelyRunBrick wouldn't be necessary because if the tab is closed, then the main runner also closes.
There was a problem hiding this comment.
Thanks, will give those notes a look
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.
What does this PR do?
Use Case Patterns Enabled
Demo Site