Page.On

[inancgumus]

What?

This is a grand issue to keep track of page.on methods and their status.

Why?

To provide an overview of the ongoing process.

How?

We have many community requests to add more event handling for other events. These event handling will enable users to perform more dynamic actions in their test when certain events occur, which can help them capture, diagnose, and assert when things are not going well or are going well.

Tasks

Tasks

Beta Give feedback

1. Evaluate each event and decide which ones give the most value.
2. Implement each event, handling the events that give the most value.
3. URL Grouping/Aggregation #371
   4 of 4
   blocked evaluate feature next user request +5
   
4. Generalize page.on events #1227
   7 of 7
   dx refactor +2
   
5. Filter out request metrics by their URL tag #1434
   feature next user request +3
6. Configurable download behavior #1289
   1 of 8
   async feature playwright +3
   
7. Implement Download handling #98
   0 of 3
   async feature playwright +3
8. Implement page.on('response') #1153
   feature playwright user request +3
9. Add support for interacting with dialog boxes #655
   feature +1
10. page.on('close')
11. page.on('console')
12. page.on('crash')
13. page.on('dialog')
14. page.on('domcontentloaded')
15. page.on('download')
16. page.on('filechooser')
17. page.on('frameattached')
18. page.on('framedetached')
19. page.on('framenavigated')
20. page.on('load')
21. page.on('pageerror')
22. page.on('popup')
23. page.on('request')
24. page.on('requestfailed')
25. page.on('requestfinished')
26. page.on('response')
27. page.on('websocket')
28. page.on('worker')
29. Implement page.on('console') to be able to assert on logs #835
    4 of 4
    feature user request +2
    
30. Detect and assert on page errors #1481
    feature playwright +2

Known issues (possibly related)

Beta Give feedback

1. Browser hangs when page.close not called when using page.on #1450
   2 of 2
   bug +1
   
2. Browser hangs for an unknown reason #1451
   bug +1