Skip to content

Commit

Permalink
Documentation: Add one more option for getting started
Browse files Browse the repository at this point in the history
Using a profiler is another great way to find issues
  • Loading branch information
yyny authored and awesomekling committed Oct 27, 2024
1 parent 8409178 commit 551b72b
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions Documentation/GettingStartedContributing.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,7 @@ Here are some of the ways you can find an issue in Ladybird:
* Manually, by using the browser as you normally would.
* By finding failing WPT tests on [WPT.fyi](https://wpt.fyi/results/?label=master&product=ladybird). Note that while fixes are welcome, you don't need to submit issue reports for individual tests.
* By finding WPT tests on [WPT.fyi](https://wpt.fyi/results/?label=master&product=ladybird) that are [timing out in Ladybird](https://wpt.fyi/results/?product=ladybird&q=status%3Atimeout). For a real-world walk-through of doing that from start to finish with an actual timing-out-in-Ladybird test case, see the [“Fixing a WPT timeout in Window.postMessage()”](https://www.youtube.com/watch?v=X4S9afzRTXs) “browser hacking” video.
* By using a profiling tool such as [Callgrind](https://valgrind.org/docs/manual/cl-manual.html) to find code that can be improved.

If you’re not necessarily already a proficient C++ programmer, beginning by troubleshooting WPT tests may be the very best way to get started contributing to the project — especially if you _do_ already have some proficiency with frontend JavaScript code.

Expand Down

0 comments on commit 551b72b

Please sign in to comment.