315009 - XForms does not initialize properly after XSLT transformation applied

Status: RESOLVED DUPLICATE of bug 294612

(Core Graveyard :: XForms, defect)

Description

[hinfoxbt]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20051103 Firefox/1.6a1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20051103 Firefox/1.6a1

After an XSLT transformation applied to the XHTML Firefox does not display initial values from the model and output element does not display text at all.

I made a simple xhtml file which uses a stylesheet with identity transformation. This can be used to reproduce the bug. If the stylesheet invocation is commented out then everything went fine.

Reproducible: Always

Steps to Reproduce:
1. Open an XForms form which uses an xslt transformation and have initial values assigned in the model.

Actual Results:  
The initial values does not display at all.

Expected Results:  
The initial values should display correctly.

The default theme was used. I could not verify that this occurs on other architectures and/or operationg systems.

Comment 1

[hinfoxbt]

Attachment: The simple xhtml file which produces the bug

Comment 2

[hinfoxbt]

Attachment: The identity transformation used on the xhtml file

Comment 3

[hinfoxbt]

Attachment: Updated testcase to reflect the discovered problem

This seems to be an initialization problem because XForms initialization events does not fire properly after an XSLT transformation regardless of what the transformation does. If the transformation does not take place (such as commented out) then they fire properly and the form also initialized properly.

Therefore I modify the summary because this reflects the problem more closely and I make this testcase.

This testcase should produce three modal alerts (one for xforms-model-construct, xforms-model-construct-done and xforms-ready) and initialize the form properly but it does not produced this alerts and the form does not initialized.

It is possible to initialize the XForms processor manually from the page? If it is then this should be a temporary workaround but I did not find anything about the manual initialization of the XForms processor.

Comment 4

[Allan Beaufour]

*** This bug has been marked as a duplicate of 294612 ***