You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Alinoor Rahman (Created) (JIRA)" <ji...@apache.org> on 2012/02/07 22:49:00 UTC

[jira] [Created] (WICKET-4394) RefreshingView odd behaviour with EditableLabel with hardcoded id in html

RefreshingView odd behaviour with EditableLabel with hardcoded id in html
-------------------------------------------------------------------------

                 Key: WICKET-4394
                 URL: https://issues.apache.org/jira/browse/WICKET-4394
             Project: Wicket
          Issue Type: Bug
          Components: wicket
    Affects Versions: 1.5.4
            Reporter: Alinoor Rahman
            Priority: Minor
         Attachments: bug.tar.gz

run the attached code, click on the link from the homepage. Then edit click on an item in the second column, which ever row you click on to edit it always goes to the top of the list, in wicket 1.4.18 the rows did not move to the stop.
I've found that this problem occurs when the id of the EditableLabel is set in the markup e.g. in RefreshingPage.html we have <p wicket:id="item" id="1">item</p>, if the id attribute is removed from the markup, everything seems to work as expected.



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Closed] (WICKET-4394) RefreshingView odd behaviour with EditableLabel with hardcoded id in html

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

Sven Meier closed WICKET-4394.
------------------------------

    Resolution: Invalid
      Assignee: Sven Meier

In Wicket 1.5 the id from your html markup takes precedence, see:

https://cwiki.apache.org/WICKET/migration-to-wicket-15.html#MigrationtoWicket1.5-Component.getMarkupId%28%29implementationchanged

In your case this leads to invalid html with multiple identical ids. Please remove the id (not wicket:id of course) from your markup.
                
> RefreshingView odd behaviour with EditableLabel with hardcoded id in html
> -------------------------------------------------------------------------
>
>                 Key: WICKET-4394
>                 URL: https://issues.apache.org/jira/browse/WICKET-4394
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5.4
>            Reporter: Alinoor Rahman
>            Assignee: Sven Meier
>            Priority: Minor
>         Attachments: bug.tar.gz
>
>
> run the attached code, click on the link from the homepage. Then click to edit an item in the second column, which ever row you click on to edit it always goes to the top of the list, in wicket 1.4.18 the rows did not move to the top.
> I've found that this problem occurs when the id of the EditableLabel is set in the markup e.g. in RefreshingPage.html we have <p wicket:id="item" id="1">item</p>, if the id attribute is removed from the markup, everything seems to work as expected.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (WICKET-4394) RefreshingView odd behaviour with EditableLabel with hardcoded id in html

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

Alinoor Rahman updated WICKET-4394:
-----------------------------------

    Description: 
run the attached code, click on the link from the homepage. Then click to edit an item in the second column, which ever row you click on to edit it always goes to the top of the list, in wicket 1.4.18 the rows did not move to the top.
I've found that this problem occurs when the id of the EditableLabel is set in the markup e.g. in RefreshingPage.html we have <p wicket:id="item" id="1">item</p>, if the id attribute is removed from the markup, everything seems to work as expected.



  was:
run the attached code, click on the link from the homepage. Then click to edit an item in the second column, which ever row you click on to edit it always goes to the top of the list, in wicket 1.4.18 the rows did not move to the stop.
I've found that this problem occurs when the id of the EditableLabel is set in the markup e.g. in RefreshingPage.html we have <p wicket:id="item" id="1">item</p>, if the id attribute is removed from the markup, everything seems to work as expected.



    
> RefreshingView odd behaviour with EditableLabel with hardcoded id in html
> -------------------------------------------------------------------------
>
>                 Key: WICKET-4394
>                 URL: https://issues.apache.org/jira/browse/WICKET-4394
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5.4
>            Reporter: Alinoor Rahman
>            Priority: Minor
>         Attachments: bug.tar.gz
>
>
> run the attached code, click on the link from the homepage. Then click to edit an item in the second column, which ever row you click on to edit it always goes to the top of the list, in wicket 1.4.18 the rows did not move to the top.
> I've found that this problem occurs when the id of the EditableLabel is set in the markup e.g. in RefreshingPage.html we have <p wicket:id="item" id="1">item</p>, if the id attribute is removed from the markup, everything seems to work as expected.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (WICKET-4394) RefreshingView odd behaviour with EditableLabel with hardcoded id in html

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

Alinoor Rahman updated WICKET-4394:
-----------------------------------

    Attachment: bug.tar.gz
    
> RefreshingView odd behaviour with EditableLabel with hardcoded id in html
> -------------------------------------------------------------------------
>
>                 Key: WICKET-4394
>                 URL: https://issues.apache.org/jira/browse/WICKET-4394
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5.4
>            Reporter: Alinoor Rahman
>            Priority: Minor
>         Attachments: bug.tar.gz
>
>
> run the attached code, click on the link from the homepage. Then edit click on an item in the second column, which ever row you click on to edit it always goes to the top of the list, in wicket 1.4.18 the rows did not move to the stop.
> I've found that this problem occurs when the id of the EditableLabel is set in the markup e.g. in RefreshingPage.html we have <p wicket:id="item" id="1">item</p>, if the id attribute is removed from the markup, everything seems to work as expected.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (WICKET-4394) RefreshingView odd behaviour with EditableLabel with hardcoded id in html

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

Alinoor Rahman updated WICKET-4394:
-----------------------------------

    Description: 
run the attached code, click on the link from the homepage. Then click to edit an item in the second column, which ever row you click on to edit it always goes to the top of the list, in wicket 1.4.18 the rows did not move to the stop.
I've found that this problem occurs when the id of the EditableLabel is set in the markup e.g. in RefreshingPage.html we have <p wicket:id="item" id="1">item</p>, if the id attribute is removed from the markup, everything seems to work as expected.



  was:
run the attached code, click on the link from the homepage. Then edit click on an item in the second column, which ever row you click on to edit it always goes to the top of the list, in wicket 1.4.18 the rows did not move to the stop.
I've found that this problem occurs when the id of the EditableLabel is set in the markup e.g. in RefreshingPage.html we have <p wicket:id="item" id="1">item</p>, if the id attribute is removed from the markup, everything seems to work as expected.



    
> RefreshingView odd behaviour with EditableLabel with hardcoded id in html
> -------------------------------------------------------------------------
>
>                 Key: WICKET-4394
>                 URL: https://issues.apache.org/jira/browse/WICKET-4394
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5.4
>            Reporter: Alinoor Rahman
>            Priority: Minor
>         Attachments: bug.tar.gz
>
>
> run the attached code, click on the link from the homepage. Then click to edit an item in the second column, which ever row you click on to edit it always goes to the top of the list, in wicket 1.4.18 the rows did not move to the stop.
> I've found that this problem occurs when the id of the EditableLabel is set in the markup e.g. in RefreshingPage.html we have <p wicket:id="item" id="1">item</p>, if the id attribute is removed from the markup, everything seems to work as expected.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira