You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Nate Roe (JIRA)" <ji...@apache.org> on 2008/07/29 19:21:32 UTC

[jira] Created: (WICKET-1762) JavaScript error when DatePicker is a child of a hidden Container

JavaScript error when DatePicker is a child of a hidden Container
-----------------------------------------------------------------

                 Key: WICKET-1762
                 URL: https://issues.apache.org/jira/browse/WICKET-1762
             Project: Wicket
          Issue Type: Bug
          Components: wicket-extensions
         Environment: I'm using JBoss 4.05 and Wicket 1.3.3, but this issue shows up on the trunk build as of July 28, 2008.  Both Firefox and IE show the error.
            Reporter: Nate Roe
            Priority: Minor


1. Add a DatePicker to a DateTextField.  
2. Add the DateTextField to a WebMarkupContainer.  
3. Set the WebMarkupContainer's visibility to false.  
4. Load the page.  

Notice JavaScript error (this.oDomContainer is null: calendar.js, line 1452).

It looks like the header contributions for the calendar are being rendered even if the calendar itself is hidden.

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


[jira] Resolved: (WICKET-1762) JavaScript error when DatePicker is a child of a hidden Container

Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg resolved WICKET-1762.
-----------------------------------

    Resolution: Cannot Reproduce
      Assignee: Igor Vaynberg

could not reproduce with 1.3.x or trunk

> JavaScript error when DatePicker is a child of a hidden Container
> -----------------------------------------------------------------
>
>                 Key: WICKET-1762
>                 URL: https://issues.apache.org/jira/browse/WICKET-1762
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-extensions
>         Environment: I'm using JBoss 4.05 and Wicket 1.3.3, but this issue shows up on the trunk build as of July 28, 2008.  Both Firefox and IE show the error.
>            Reporter: Nate Roe
>            Assignee: Igor Vaynberg
>            Priority: Minor
>         Attachments: WicketTest.rar
>
>
> 1. Add a DatePicker to a DateTextField.  
> 2. Add the DateTextField to a WebMarkupContainer.  
> 3. Set the WebMarkupContainer's visibility to false.  
> 4. Load the page.  
> Notice JavaScript error (this.oDomContainer is null: calendar.js, line 1452).
> It looks like the header contributions for the calendar are being rendered even if the calendar itself is hidden.

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


[jira] Updated: (WICKET-1762) JavaScript error when DatePicker is a child of a hidden Container

Posted by "Nate Roe (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nate Roe updated WICKET-1762:
-----------------------------

    Attachment: WicketTest.rar

Simple application that demonstrates the issue.

> JavaScript error when DatePicker is a child of a hidden Container
> -----------------------------------------------------------------
>
>                 Key: WICKET-1762
>                 URL: https://issues.apache.org/jira/browse/WICKET-1762
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-extensions
>         Environment: I'm using JBoss 4.05 and Wicket 1.3.3, but this issue shows up on the trunk build as of July 28, 2008.  Both Firefox and IE show the error.
>            Reporter: Nate Roe
>            Priority: Minor
>         Attachments: WicketTest.rar
>
>
> 1. Add a DatePicker to a DateTextField.  
> 2. Add the DateTextField to a WebMarkupContainer.  
> 3. Set the WebMarkupContainer's visibility to false.  
> 4. Load the page.  
> Notice JavaScript error (this.oDomContainer is null: calendar.js, line 1452).
> It looks like the header contributions for the calendar are being rendered even if the calendar itself is hidden.

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