As far as I'm concerned, I think it just needs lots of exposure to many different kinds of users. This argues for extended baking on both trunk and beta (possibly for longer than a single update cycle on each). I have no idea what kinds of problems might occur, and so have no specific ideas how to test for them. Jeff might have some ideas, though.
Bug 1734705 Comment 26 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
As far as I'm concerned, I think it just needs lots of exposure to many different kinds of users. This argues for extended baking on both trunk and beta (possibly for longer than a single update cycle on each). I have no idea what kinds of problems might occur, and so have no specific ideas how to test for them. Jeff might have some ideas, though. Edit: On second thought, it'd be worthwhile to test for native event starvation (if we can figure out how to do that). The current patch stops all processing of native events while `aMayWait` is false.
As far as I'm concerned, I think it just needs lots of exposure to many different kinds of users. This argues for extended baking on both trunk and beta (possibly for longer than a single update cycle on each). I have no idea what kinds of problems might occur, and so have no specific ideas how to test for them. Jeff might have some ideas, though. Edit: On second thought, it'd be worthwhile to test for native event starvation (if we can figure out how to do that). The current patch stops all processing of native events by `nsAppShell::ProcessNextNativeEvent()` while `aMayWait` is false.