You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Bruno Aranda (JIRA)" <de...@myfaces.apache.org> on 2007/05/17 22:46:16 UTC

[jira] Created: (MYFACES-1633) Incorret view rendering after postback

Incorret view rendering after postback
--------------------------------------

                 Key: MYFACES-1633
                 URL: https://issues.apache.org/jira/browse/MYFACES-1633
             Project: MyFaces Core
          Issue Type: Bug
          Components: JSR-252
    Affects Versions: 1.2.0-SNAPSHOT
            Reporter: Bruno Aranda
            Priority: Critical


The rendered code and the html code from the page are not ordered correctly. Visual mess.

Easily observable when running the simple examples with our 1.2 implementation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (MYFACES-1633) Incorret view rendering after postback

Posted by "Bruno Aranda (JIRA)" <de...@myfaces.apache.org>.
     [ https://issues.apache.org/jira/browse/MYFACES-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruno Aranda resolved MYFACES-1633.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.0-SNAPSHOT

New IDs where generated on post back for components that already had one due to a bug in the generation of the id. Components where inserted in the wrong place as the list of component IDs and the actual child components for a parent where different.

> Incorret view rendering after postback
> --------------------------------------
>
>                 Key: MYFACES-1633
>                 URL: https://issues.apache.org/jira/browse/MYFACES-1633
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-252
>    Affects Versions: 1.2.0-SNAPSHOT
>            Reporter: Bruno Aranda
>         Assigned To: Bruno Aranda
>            Priority: Blocker
>             Fix For: 1.2.0-SNAPSHOT
>
>
> The rendered code and the html code from the page are not ordered correctly. Visual mess.
> Easily observable when running the simple examples with our 1.2 implementation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (MYFACES-1633) Incorret view rendering after postback

Posted by "Bruno Aranda (JIRA)" <de...@myfaces.apache.org>.
    [ https://issues.apache.org/jira/browse/MYFACES-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496996 ] 

Bruno Aranda commented on MYFACES-1633:
---------------------------------------

A snippet as simple as this can reproduce the issue:

<f:view>
        <h:outputLabel value="LABEL"/>

        <h:form id="form">
            <h:commandButton id="button" value="BUTTON" action="none" />
        </h:form>

        <h:outputLabel value="END"/>
</f:view>

When the button is clicked, the form is moved to the bottom. Seems to be an issue in UIComponentClassicTagBase or in the rendering of the view. If the end label has id, everything is all right, of if everything is nested in another component (e.g. panelGroup). If the id of the form is removed, everything works ok too.

I will investigate further on sunday...


> Incorret view rendering after postback
> --------------------------------------
>
>                 Key: MYFACES-1633
>                 URL: https://issues.apache.org/jira/browse/MYFACES-1633
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-252
>    Affects Versions: 1.2.0-SNAPSHOT
>            Reporter: Bruno Aranda
>         Assigned To: Bruno Aranda
>            Priority: Blocker
>
> The rendered code and the html code from the page are not ordered correctly. Visual mess.
> Easily observable when running the simple examples with our 1.2 implementation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (MYFACES-1633) Incorret view rendering after postback

Posted by "Paul McMahan (JIRA)" <de...@myfaces.apache.org>.
    [ https://issues.apache.org/jira/browse/MYFACES-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496686 ] 

Paul McMahan commented on MYFACES-1633:
---------------------------------------

Bruno, is GERONIMO-3167 a manifestation of this problem?

> Incorret view rendering after postback
> --------------------------------------
>
>                 Key: MYFACES-1633
>                 URL: https://issues.apache.org/jira/browse/MYFACES-1633
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-252
>    Affects Versions: 1.2.0-SNAPSHOT
>            Reporter: Bruno Aranda
>            Priority: Critical
>
> The rendered code and the html code from the page are not ordered correctly. Visual mess.
> Easily observable when running the simple examples with our 1.2 implementation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (MYFACES-1633) Incorret view rendering after postback

Posted by "Bruno Aranda (JIRA)" <de...@myfaces.apache.org>.
    [ https://issues.apache.org/jira/browse/MYFACES-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496689 ] 

Bruno Aranda commented on MYFACES-1633:
---------------------------------------

Yes, exactly, this is the same problem. 

I am raising the priority to blocker, as IMO we cannot release with such an outstanding bug.

> Incorret view rendering after postback
> --------------------------------------
>
>                 Key: MYFACES-1633
>                 URL: https://issues.apache.org/jira/browse/MYFACES-1633
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-252
>    Affects Versions: 1.2.0-SNAPSHOT
>            Reporter: Bruno Aranda
>            Priority: Critical
>
> The rendered code and the html code from the page are not ordered correctly. Visual mess.
> Easily observable when running the simple examples with our 1.2 implementation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.