My plan for this is the following: In this bug, change all affected tests to set `widget.macos.native-context-menus` to `false`. This will keep the tree green even as the default is flipped to true, and it will retain existing test coverage. However, it means that tests will be running under a different configuration from what we're shipping to users. Then, in follow-up bugs: 1. Increase testability of native context menus. For example, some tests open a context menu and then use menuitem.click(). Maybe we can make that work for native context menus so that existing tests just work. In any case, there will need to be some kind of API to open a native context menu and activate an item in it. 2. Incrementally convert tests to use the agnostic APIs so that they no longer need to override the pref.
Bug 1700724 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
My plan for this is the following: In this bug, change all affected tests to set `widget.macos.native-context-menus` to `false`. This will keep the tree green even as the default is flipped to true, and it will retain existing test coverage. However, it means that tests will be running under a different configuration from what we're shipping to users. Then, in follow-up bugs: 1. Make sure it's easy to write tests that work with native context menus. For example, some tests open a context menu and then use menuitem.click(). Maybe we can make that work for native context menus so that existing tests just work. In any case, there will need to be some kind of API to open a native context menu and activate an item in it. 2. Incrementally convert tests to use the agnostic APIs so that they no longer need to override the pref.
Edit: This comment is no longer accurate, see comment 7. My plan for this is the following: In this bug, change all affected tests to set `widget.macos.native-context-menus` to `false`. This will keep the tree green even as the default is flipped to true, and it will retain existing test coverage. However, it means that tests will be running under a different configuration from what we're shipping to users. Then, in follow-up bugs: 1. Make sure it's easy to write tests that work with native context menus. For example, some tests open a context menu and then use menuitem.click(). Maybe we can make that work for native context menus so that existing tests just work. In any case, there will need to be some kind of API to open a native context menu and activate an item in it. 2. Incrementally convert tests to use the agnostic APIs so that they no longer need to override the pref.