Closed Bug 1802192 Opened 3 years ago Closed 2 years ago

Re-enable macOS fullscreen tests

Categories

(Core :: Widget: Cocoa, defect, P3)

Unspecified
macOS
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: bradwerth, Assigned: bradwerth)

References

Details

Bug 1631735 disabled some macOS fullscreen tests that failed due to changes in our use of the macOS fullscreen API. The problems in these tests do not seem to appear during interactive fullscreen browser usage, but we still want the test coverage, so these tests and/or the code need to be fixed. The tests need to work with both true and false values of the full-screen-api.macos-native-full-screen pref.

Blocks: 1802193
Severity: -- → S3
Priority: -- → P3

Re-enabling these tests will involve some combination of...

  1. Defining a new event to be fired when the fullscreen transition is complete. Most tests are waiting for the sizemode event, which is fired at the beginning of the transition. Presently, there is no event sent at the end of the transition.
  2. Make nsCocoaWindow respond to requests to minimize the window during a transition, similar to how it handles requests to undo the fullscreen state or to set the window's visibility during a transition.

Hi Brad, with the change on bug 1631735 we basically have a regression for WebDriver when users want to manipulate the window after leaving fullscreen mode. We don't know how many folks would be affected by that, so it raises a question for us when we can get these tests working again for headfull mode. Do you have an estimate when this bug can / will be fixed? Could it happen for the 110 release? Thanks.

Flags: needinfo?(bwerth)

I hope to revise and re-land Bug 1631735 with no impact to Webdriver tests, which will allow this Bug to be closed as INVALID.

Flags: needinfo?(bwerth)

After many changes, Bug 1631735 landed without disabling any existing tests. No work to do here.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.