Bug 2368 - Add a test for OnFormClosing behaviour.
Summary: Add a test for OnFormClosing behaviour.
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: Windows.Forms ()
Version: 2.10.x
Hardware: All All
: Lowest normal
Target Milestone: Community
Assignee: Bugzilla
Depends on:
Reported: 2011-12-06 12:13 UTC by Aaron
Modified: 2017-09-01 11:56 UTC (History)
1 user (show)

Tags: mono-community
Is this bug a regression?: ---
Last known good build:

This is a possible test for the desired functionality. (792 bytes, text/plain)
2011-12-06 12:13 UTC, Aaron

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 2368 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Aaron 2011-12-06 12:13:45 UTC
Created attachment 1003 [details]
This is a possible test for the desired functionality.

The System.Windows.Forms.Form.OnFormClosing implementation should allow a later registered handler to override an earlier handler's cancel request.  This behaviour is observed in Windows, and, from what I can tell of the code, should be  observed in Mono.  I submit this test not because Mono is behaving incorrectly, but because this behaviour should be made explicit (it's not in the MSDN docs).