Skip to content
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

Remove `origin` parameter from `Worker::handle_message` #25426

Merged
merged 1 commit into from Jan 4, 2020

Conversation

@kunalmohan
Copy link
Collaborator

kunalmohan commented Jan 3, 2020

Test in workers/interfaces/DedicatedWorkerGlobalScope/postMessage/message-event.html was failing because worker.onmessage was seeing non-empty event.origin. Removing origin parameter from Worker::handle_message and sending None to MessageEvent::dispatch_jsval solves the issue.

r?@jdm


  • ./mach build -d does not report any errors
  • ./mach test-tidy does not report any errors
  • These changes fix #25149 (GitHub issue number if applicable)
  • There are tests for these changes
@highfive
Copy link

highfive commented Jan 3, 2020

Heads up! This PR modifies the following files:

  • @asajeffrey: components/script/dom/worker.rs, components/script/dom/dedicatedworkerglobalscope.rs
  • @KiChjang: components/script/dom/worker.rs, components/script/dom/dedicatedworkerglobalscope.rs
@jdm
Copy link
Member

jdm commented Jan 3, 2020

@bors-servo try=wpt

bors-servo added a commit that referenced this pull request Jan 3, 2020
Remove `origin` parameter from `Worker::handle_message`

<!-- Please describe your changes on the following line: -->
Test in  `workers/interfaces/DedicatedWorkerGlobalScope/postMessage/message-event.html` was failing because worker.onmessage was seeing non-empty event.origin. Removing `origin` parameter from `Worker::handle_message` and sending `None` to `MessageEvent::dispatch_jsval` solves the issue.

r?@jdm

---
<!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: -->
- [X] `./mach build -d` does not report any errors
- [X] `./mach test-tidy` does not report any errors
- [X] These changes fix #25149  (GitHub issue number if applicable)

<!-- Either: -->
- [X] There are tests for these changes

<!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.-->

<!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
@bors-servo
Copy link
Contributor

bors-servo commented Jan 3, 2020

Trying commit 0692a26 with merge b0c4bea...

@bors-servo
Copy link
Contributor

bors-servo commented Jan 3, 2020

☀️ Test successful - status-taskcluster
State: approved= try=True

@jdm
Copy link
Member

jdm commented Jan 3, 2020

@bors-servo r+
Thanks!

@bors-servo
Copy link
Contributor

bors-servo commented Jan 3, 2020

📌 Commit 0692a26 has been approved by jdm

@bors-servo
Copy link
Contributor

bors-servo commented Jan 4, 2020

Testing commit 0692a26 with merge 55afdde...

bors-servo added a commit that referenced this pull request Jan 4, 2020
Remove `origin` parameter from `Worker::handle_message`

<!-- Please describe your changes on the following line: -->
Test in  `workers/interfaces/DedicatedWorkerGlobalScope/postMessage/message-event.html` was failing because worker.onmessage was seeing non-empty event.origin. Removing `origin` parameter from `Worker::handle_message` and sending `None` to `MessageEvent::dispatch_jsval` solves the issue.

r?@jdm

---
<!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: -->
- [X] `./mach build -d` does not report any errors
- [X] `./mach test-tidy` does not report any errors
- [X] These changes fix #25149  (GitHub issue number if applicable)

<!-- Either: -->
- [X] There are tests for these changes

<!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.-->

<!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
@bors-servo
Copy link
Contributor

bors-servo commented Jan 4, 2020

💔 Test failed - status-taskcluster

@jdm
Copy link
Member

jdm commented Jan 4, 2020

@bors-servo
Copy link
Contributor

bors-servo commented Jan 4, 2020

Testing commit 0692a26 with merge afa1b85...

bors-servo added a commit that referenced this pull request Jan 4, 2020
Remove `origin` parameter from `Worker::handle_message`

<!-- Please describe your changes on the following line: -->
Test in  `workers/interfaces/DedicatedWorkerGlobalScope/postMessage/message-event.html` was failing because worker.onmessage was seeing non-empty event.origin. Removing `origin` parameter from `Worker::handle_message` and sending `None` to `MessageEvent::dispatch_jsval` solves the issue.

r?@jdm

---
<!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: -->
- [X] `./mach build -d` does not report any errors
- [X] `./mach test-tidy` does not report any errors
- [X] These changes fix #25149  (GitHub issue number if applicable)

<!-- Either: -->
- [X] There are tests for these changes

<!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.-->

<!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
@bors-servo
Copy link
Contributor

bors-servo commented Jan 4, 2020

☀️ Test successful - status-taskcluster
Approved by: jdm
Pushing afa1b85 to master...

@bors-servo bors-servo merged commit 0692a26 into servo:master Jan 4, 2020
2 checks passed
2 checks passed
Community-TC (pull_request) TaskGroup: success
Details
homu Test successful
Details
@kunalmohan kunalmohan deleted the kunalmohan:25149-EventOrigin branch Jan 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

4 participants
You can’t perform that action at this time.