[Mono-bugs] [Bug 471305] New: Control lifecycle inconsistency between Mono and MS.NET implementations

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Sat Jan 31 15:11:53 EST 2009


           Summary: Control lifecycle inconsistency between Mono and
                    MS.NET implementations
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.2.x
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Sys.Web
        AssignedTo: mhabersack at novell.com
        ReportedBy: sergey.hakobyan at gaiaware.net
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---

Created an attachment (id=269091)
 --> (https://bugzilla.novell.com/attachment.cgi?id=269091)
Failing testcase

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:
Gecko/2008120122 Firefox/3.0.5

There is a inconsistency between the control lifecycle in Mono and MS.NET when
the control is being rearranged ( for example Added -> Removed -> Added to the
same Controls collection, to the same position ).

In MS.NET OnInit() method of the control won't be called on second addition,
because the private ControlState will still be >= Initialized. While in Mono
OnInit() will be called and will lead to lots of problems with custom controls
in dynamic scenarios.

Simplistic/minimalistic testcase to reproduce the problem is attached.
In MS.NET only 1 Label is added to the page, in Mono - 2 are added.

Reproducible: Always

Steps to Reproduce:
1. Download and extract the attachment
2. Run xsp2
3. Start the browser and open the Default.aspx
Actual Results:  
Two labels are added to the page

Expected Results:  
One label should be added to the page

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the mono-bugs mailing list