Closed Bug 1706775 Opened 5 years ago Closed 5 years ago

Ensure that various menu tests under toolkit/content/tests/chrome are run on non-native menus

Categories

(Core :: Widget: Cocoa, task)

All
macOS
task

Tracking

()

RESOLVED FIXED
90 Branch
Tracking Status
firefox89 --- fixed
firefox90 --- fixed

People

(Reporter: mstange, Assigned: mstange)

References

Details

(Whiteboard: [proton-uplift])

Attachments

(1 file)

The following tests are meant to exercise our non-native menu code:

toolkit/content/tests/chrome/test_contextmenu_list.xhtml
toolkit/content/tests/chrome/test_largemenu.html
toolkit/content/tests/chrome/test_popup_attribute.xhtml
toolkit/content/tests/chrome/test_popup_button.xhtml

When native context menus are enabled, we do not use our non-native menu code for context menus any more. However, we still use the code for other popups which are not context menus, for example for toolbar button dropdowns. As long as this is the case, we should keep our test coverage of non-native menu code on macOS.
We can achieve this by setting the pref widget.macos.native-context-menus to false in these tests.

There are some aspects of these tests which are worth testing on native context menus, too. I'm planning to make a list of those aspects and put it into bug 1700727, and then add separate tests for them as a follow-up. That way, our "menu implementation" tests will be neatly split into separate files: Some files which only test the non-native implementation, and some files which only test the native implementation.
And we also have a whole host of tests which are implementation-agnostic - any test which calls activateItem, for example.

These tests are meant to exercise our non-native menu code.
Some aspects of these tests are worth testing with native menus, too -
we will have separate native menu test files for those.

Once we do not use non-native menus anywhere on macOS anymore, we can
disable these tests on macOS. However, for now, we still use non-native
menus for 'anchored popups', e.g. toolbar button dropdowns.
In order to retain test coverage for our non-native menu code, we make
sure that these tests are run with native context menus turned off.

Pushed by mstange@themasta.com: https://hg.mozilla.org/integration/autoland/rev/c376b409702c Ensure that various menu tests under toolkit/content/tests/chrome are run on non-native menus. r=harry
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → 90 Branch
Whiteboard: [proton-uplift]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: