1. 15 Aug, 2022 1 commit
    • Justin Wernick's avatar
      Fix #322 - Ensure that content filters continue to work when service workers are suspended · 0f3ef153
      Justin Wernick authored
      It appears that the fix added in #133 (back when we didn't have
      any proper MV3 testing support) is actually good!
      
      This MR mostly extends the testing to make sure it's reliable in
      the service worker fuzzing tests (by allowing increased
      timeouts), and adds a few new test cases for areas that I found
      weren't adequately covered.
      
      As part of this issue, I also reviewed the content filter code
      for anything else that might cause problems when the service
      workers are suspended:
      
      - Content filters do not need to maintain state between multiple events.
      - Content filters do not emit events (except for onBlockableItem events,
        which will be handled as part in #320)
      - Content filters use frame state and the filter engine, so need to ensure
        that those are initialized before they are used.
      - Sitekeys will still be lost when the service worker is suspended, so
        those will not work correctly, but sitekey support in MV3 is a later problem.
      0f3ef153
  2. 12 Aug, 2022 3 commits
  3. 11 Aug, 2022 4 commits
  4. 10 Aug, 2022 1 commit
  5. 05 Aug, 2022 3 commits
  6. 29 Jul, 2022 1 commit
  7. 28 Jul, 2022 6 commits
  8. 26 Jul, 2022 3 commits
  9. 25 Jul, 2022 1 commit
  10. 19 Jul, 2022 1 commit
  11. 18 Jul, 2022 1 commit
  12. 15 Jul, 2022 1 commit
  13. 14 Jul, 2022 4 commits
  14. 12 Jul, 2022 4 commits
  15. 10 Jul, 2022 1 commit
    • Justin Wernick's avatar
      Fix #217 - Add a test suspends the MV3 service worker · 2b3134af
      Justin Wernick authored
      This commit adds the ability for us to suspend service workers in a unit test.
      
      To do this, it created a mechanism for a test to ask Selenium to open Chrome's service worker debugging page and click the "stop" button. The service worker should start up again automatically when it next gets an event.
      
      In the CI environment with limited CPU and memory, this often causes large lag spikes in the run, so I've increased the default Mocha timeout for MV3 tests in CI.
      2b3134af
  16. 07 Jul, 2022 2 commits
  17. 06 Jul, 2022 2 commits
  18. 05 Jul, 2022 1 commit