| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
Thank you for adding WPT test. I left some comments. But they are small things so it is ok not to fix them :)
Sorry, something went wrong.
|
@shisama Thank you for reviews! Other member react your suggestion, so I will incorporate your correction. |
Sorry, something went wrong.
Co-authored-by: Masashi Hirano <shisama07@gmail.com>
Co-authored-by: Masashi Hirano <shisama07@gmail.com>
|
@bnoordhuis |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM, thanks!
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
|
We could remove the following test, given they are already implemented in js in the latest wpt repo:
We could do the cleanup either in a separate pr or in this pr. I will be fine with both approaches. |
Sorry, something went wrong.
|
@F3n67u |
Sorry, something went wrong.
PR-URL: nodejs/node#43151 Refs: nodejs/node#40678 Reviewed-By: Masashi Hirano <shisama07@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com>
| Back | FazBrowse Home | New Git URL |
Following the comment #40678 (comment), I added WPT tests for dom/events. The files except test/wpt/status/dom/events.json, test/wpt/test-events.js were generated by git-node wpt dom/events.
Currently, some tests are failed. Is it OK? or should I make some work for passing them? Many of them seem to fail due to lack of browser specific API like document is not undefined.
Refs: #40678