You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Andy Schwartz (JIRA)" <de...@myfaces.apache.org> on 2011/08/16 19:17:28 UTC

[jira] [Created] (TRINIDAD-2129) Component showcase demo broken

Component showcase demo broken
------------------------------

                 Key: TRINIDAD-2129
                 URL: https://issues.apache.org/jira/browse/TRINIDAD-2129
             Project: MyFaces Trinidad
          Issue Type: Bug
         Environment: Tested on GlassFish v3.1, though not sure that is significant.  Repros in various browsers (FF, Safari, Chrome).
            Reporter: Andy Schwartz


The "Browse Components" accordion in the component showcase demo is not working.  It is not possible to disclose any accordion pane.

Interestingly, the standalone panelAccordion demo under the trinidad-demo example does work without problem.

Specifying priority as "major" (and possibly should be higher) as it is possible that this is a symptom of a more fundamental problem.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (TRINIDAD-2129) Component showcase demo broken

Posted by "Max Starets (JIRA)" <de...@myfaces.apache.org>.
    [ https://issues.apache.org/jira/browse/TRINIDAD-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085964#comment-13085964 ] 

Max Starets commented on TRINIDAD-2129:
---------------------------------------

The issue is that RI's BaseTableRenderer is using writeText(Object text, UIComponent component, String  propertyName), which is not overridden in PPRResponseWriter (the method was added in JSF 1.2). This produces white space in PPR response, which is not tolerated by JSF Ajax response processing. The old legacy Trinidad PPR response processor was just skipping the white space, so we never ran into this problem. Introducing writeText override in PPRResponseWriter fixes the issue.

> Component showcase demo broken
> ------------------------------
>
>                 Key: TRINIDAD-2129
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-2129
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>         Environment: Tested on GlassFish v3.1, though not sure that is significant.  Repros in various browsers (FF, Safari, Chrome).
>            Reporter: Andy Schwartz
>
> The "Browse Components" accordion in the component showcase demo is not working.  It is not possible to disclose any accordion pane.
> Interestingly, the standalone panelAccordion demo under the trinidad-demo example does work without problem.
> Specifying priority as "major" (and possibly should be higher) as it is possible that this is a symptom of a more fundamental problem.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (TRINIDAD-2129) Component showcase demo broken

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

Max Starets resolved TRINIDAD-2129.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.1

> Component showcase demo broken
> ------------------------------
>
>                 Key: TRINIDAD-2129
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-2129
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>         Environment: Tested on GlassFish v3.1, though not sure that is significant.  Repros in various browsers (FF, Safari, Chrome).
>            Reporter: Andy Schwartz
>            Assignee: Max Starets
>             Fix For: 2.0.1
>
>         Attachments: TRINIDAD-2129.patch
>
>
> The "Browse Components" accordion in the component showcase demo is not working.  It is not possible to disclose any accordion pane.
> Interestingly, the standalone panelAccordion demo under the trinidad-demo example does work without problem.
> Specifying priority as "major" (and possibly should be higher) as it is possible that this is a symptom of a more fundamental problem.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (TRINIDAD-2129) Component showcase demo broken

Posted by "Andy Schwartz (JIRA)" <de...@myfaces.apache.org>.
    [ https://issues.apache.org/jira/browse/TRINIDAD-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085873#comment-13085873 ] 

Andy Schwartz commented on TRINIDAD-2129:
-----------------------------------------

This works (somewhat) better when running in Jetty against MyFaces.  The panelAccordion is functional, though on every other click I see a "component with duplicate id <foo> found" error (IllegalStateException). 

> Component showcase demo broken
> ------------------------------
>
>                 Key: TRINIDAD-2129
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-2129
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>         Environment: Tested on GlassFish v3.1, though not sure that is significant.  Repros in various browsers (FF, Safari, Chrome).
>            Reporter: Andy Schwartz
>
> The "Browse Components" accordion in the component showcase demo is not working.  It is not possible to disclose any accordion pane.
> Interestingly, the standalone panelAccordion demo under the trinidad-demo example does work without problem.
> Specifying priority as "major" (and possibly should be higher) as it is possible that this is a symptom of a more fundamental problem.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira