You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Nick Pratt (Created) (JIRA)" <ji...@apache.org> on 2012/01/17 01:05:39 UTC

[jira] [Created] (WICKET-4339) Possible bug with 1.5 and WiQuery (might be a WiQuery problem)

Possible bug with 1.5 and WiQuery (might be a WiQuery problem)
--------------------------------------------------------------

                 Key: WICKET-4339
                 URL: https://issues.apache.org/jira/browse/WICKET-4339
             Project: Wicket
          Issue Type: Bug
            Reporter: Nick Pratt


See attached quickstart + unit tests

--
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-4339) Possible bug with 1.5 and WiQuery (might be a WiQuery problem)

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

Andrea Del Bene updated WICKET-4339:
------------------------------------

    Attachment: autocomplete.zip
    
> Possible bug with 1.5 and WiQuery (might be a WiQuery problem)
> --------------------------------------------------------------
>
>                 Key: WICKET-4339
>                 URL: https://issues.apache.org/jira/browse/WICKET-4339
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.5.3
>            Reporter: Nick Pratt
>         Attachments: AutoCompleteProblem.tar.gz, autocomplete.zip
>
>
> See attached quickstart + unit tests.  Unsure if this is a Wicket or a WiQuery problem.

--
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] [Resolved] (WICKET-4339) Possible bug with 1.5 and WiQuery (might be a WiQuery problem)

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

Martin Grigorov resolved WICKET-4339.
-------------------------------------

    Resolution: Not A Problem

I moved the problem to WiQuery's issue tracker: http://code.google.com/p/wiquery/issues/detail?id=231
                
> Possible bug with 1.5 and WiQuery (might be a WiQuery problem)
> --------------------------------------------------------------
>
>                 Key: WICKET-4339
>                 URL: https://issues.apache.org/jira/browse/WICKET-4339
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.5.3
>            Reporter: Nick Pratt
>         Attachments: AutoCompleteProblem.tar.gz, autocomplete.zip
>
>
> See attached quickstart + unit tests.  Unsure if this is a Wicket or a WiQuery problem.

--
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] [Issue Comment Edited] (WICKET-4339) Possible bug with 1.5 and WiQuery (might be a WiQuery problem)

Posted by "Andrea Del Bene (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190495#comment-13190495 ] 

Andrea Del Bene edited comment on WICKET-4339 at 1/21/12 6:21 PM:
------------------------------------------------------------------

Hi Nick,

in the code you have attached there's no clue of WiQuery. Your unit test seems to contains some errors, for example you refer to autocomplete with the id "ddc" and not with "roles".

However I've find a weird behaviour  with WiQuery which might be a bug of this library. If I run the autocomplete example with wiquery in the classpath, the Wicket autocomplete won't work because jquery will be used instead of regular JavaScript code when component is initialized (i.e. '$(document).ready(function(event){new Wicket.AutoComplete' etc...).
Removing WiQuery jars everything works fine and regular JavaScript is used (i.e. 'Wicket.Event.add(window, "domready",' etc...).

See my quickstart for further details.
                
      was (Author: bitstorm):
    Hi Nick,

in the code you have attached there's no clue of WiQuery. Your unit test seems to contains some errors, for example you refer to autocomplete with the id "ddc" and not with "roles".

However I've find a weird behaviour  with WiQuery which might be a bug of this library. If I run the autocomplete example with wiquery in the classpath, the Wicket autocomplete won't work because jquery will be used instead of regular JavaScript code when component is initialize (i.e. '$(document).ready(function(event){new Wicket.AutoComplete' etc...).
Removing WiQuery jars everything works fine and regular JavaScript is used (i.e. 'Wicket.Event.add(window, "domready",' etc...).

See my quickstart for further details.
                  
> Possible bug with 1.5 and WiQuery (might be a WiQuery problem)
> --------------------------------------------------------------
>
>                 Key: WICKET-4339
>                 URL: https://issues.apache.org/jira/browse/WICKET-4339
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.5.3
>            Reporter: Nick Pratt
>         Attachments: AutoCompleteProblem.tar.gz, autocomplete.zip
>
>
> See attached quickstart + unit tests.  Unsure if this is a Wicket or a WiQuery problem.

--
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-4339) Possible bug with 1.5 and WiQuery (might be a WiQuery problem)

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

Nick Pratt updated WICKET-4339:
-------------------------------

    Attachment: AutoCompleteProblem.tar.gz
    
> Possible bug with 1.5 and WiQuery (might be a WiQuery problem)
> --------------------------------------------------------------
>
>                 Key: WICKET-4339
>                 URL: https://issues.apache.org/jira/browse/WICKET-4339
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.5.3
>            Reporter: Nick Pratt
>         Attachments: AutoCompleteProblem.tar.gz
>
>
> See attached quickstart + unit tests

--
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] [Issue Comment Edited] (WICKET-4339) Possible bug with 1.5 and WiQuery (might be a WiQuery problem)

Posted by "Andrea Del Bene (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190495#comment-13190495 ] 

Andrea Del Bene edited comment on WICKET-4339 at 1/21/12 6:26 PM:
------------------------------------------------------------------

Hi Nick,

in the code you have attached there's no clue of WiQuery. Your unit test seems to contains some errors, for example you refer to autocomplete with the id "ddc" and not with "roles".

However I've found a weird behaviour  with WiQuery which might be a bug of this library. If I run the autocomplete example with wiquery in the classpath, the Wicket autocomplete won't work because jquery will be used instead of regular JavaScript code when component is initialized (i.e. '$(document).ready(function(event){new Wicket.AutoComplete' etc...).
Removing WiQuery jars everything works fine and regular JavaScript is used (i.e. 'Wicket.Event.add(window, "domready",' etc...).

See my quickstart for further details.
                
      was (Author: bitstorm):
    Hi Nick,

in the code you have attached there's no clue of WiQuery. Your unit test seems to contains some errors, for example you refer to autocomplete with the id "ddc" and not with "roles".

However I've find a weird behaviour  with WiQuery which might be a bug of this library. If I run the autocomplete example with wiquery in the classpath, the Wicket autocomplete won't work because jquery will be used instead of regular JavaScript code when component is initialized (i.e. '$(document).ready(function(event){new Wicket.AutoComplete' etc...).
Removing WiQuery jars everything works fine and regular JavaScript is used (i.e. 'Wicket.Event.add(window, "domready",' etc...).

See my quickstart for further details.
                  
> Possible bug with 1.5 and WiQuery (might be a WiQuery problem)
> --------------------------------------------------------------
>
>                 Key: WICKET-4339
>                 URL: https://issues.apache.org/jira/browse/WICKET-4339
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.5.3
>            Reporter: Nick Pratt
>         Attachments: AutoCompleteProblem.tar.gz, autocomplete.zip
>
>
> See attached quickstart + unit tests.  Unsure if this is a Wicket or a WiQuery problem.

--
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] [Issue Comment Edited] (WICKET-4339) Possible bug with 1.5 and WiQuery (might be a WiQuery problem)

Posted by "Andrea Del Bene (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190495#comment-13190495 ] 

Andrea Del Bene edited comment on WICKET-4339 at 1/21/12 6:20 PM:
------------------------------------------------------------------

Hi Nick,

in the code you have attached there's no clue of WiQuery. Your unit test seems to contains some errors, for example you refer to autocomplete with the id "ddc" and not with "roles".

However I've find a weird behaviour  with WiQuery which might be a bug of this library. If I run the autocomplete example with wiquery in the classpath, the Wicket autocomplete won't work because jquery will be used instead of regular JavaScript code when component is initialize (i.e. '$(document).ready(function(event){new Wicket.AutoComplete' etc...).
Removing WiQuery jars everything works fine and regular JavaScript is used (i.e. 'Wicket.Event.add(window, "domready",' etc...).

See my quickstart for further details.
                
      was (Author: bitstorm):
    Hi Nick,

in the code you have attached ther's no clue of WiQuery. Your unit test seems to contains some errors, for example you refer to autocomplete with the id "ddc" and not with "roles".

However I've find a weird behaviour  of WiQuery which might a bug of this library. If I run the autocomplete example with wiquery in the classpath, the Wicket autocomplete won't work because jquery will be used instead of regular JavaScript code when component is initialize (i.e. '$(document).ready(function(event){new Wicket.AutoComplete' etc...).
Removing WiQuery jars everything works fine and regular JavaScript is used (i.e. 'Wicket.Event.add(window, "domready",' etc...).

See my quickstart for further details.
                  
> Possible bug with 1.5 and WiQuery (might be a WiQuery problem)
> --------------------------------------------------------------
>
>                 Key: WICKET-4339
>                 URL: https://issues.apache.org/jira/browse/WICKET-4339
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.5.3
>            Reporter: Nick Pratt
>         Attachments: AutoCompleteProblem.tar.gz, autocomplete.zip
>
>
> See attached quickstart + unit tests.  Unsure if this is a Wicket or a WiQuery problem.

--
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] [Commented] (WICKET-4339) Possible bug with 1.5 and WiQuery (might be a WiQuery problem)

Posted by "Martin Grigorov (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187334#comment-13187334 ] 

Martin Grigorov commented on WICKET-4339:
-----------------------------------------

Can you please give more details.
Thanks!
                
> Possible bug with 1.5 and WiQuery (might be a WiQuery problem)
> --------------------------------------------------------------
>
>                 Key: WICKET-4339
>                 URL: https://issues.apache.org/jira/browse/WICKET-4339
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.5.3
>            Reporter: Nick Pratt
>         Attachments: AutoCompleteProblem.tar.gz
>
>
> See attached quickstart + unit tests.  Unsure if this is a Wicket or a WiQuery problem.

--
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] [Commented] (WICKET-4339) Possible bug with 1.5 and WiQuery (might be a WiQuery problem)

Posted by "Hielke Hoeve (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206836#comment-13206836 ] 

Hielke Hoeve commented on WICKET-4339:
--------------------------------------

This issue has been fixed per WiQuery 1.5.4.
                
> Possible bug with 1.5 and WiQuery (might be a WiQuery problem)
> --------------------------------------------------------------
>
>                 Key: WICKET-4339
>                 URL: https://issues.apache.org/jira/browse/WICKET-4339
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.5.3
>            Reporter: Nick Pratt
>         Attachments: AutoCompleteProblem.tar.gz, autocomplete.zip
>
>
> See attached quickstart + unit tests.  Unsure if this is a Wicket or a WiQuery problem.

--
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] [Commented] (WICKET-4339) Possible bug with 1.5 and WiQuery (might be a WiQuery problem)

Posted by "Andrea Del Bene (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190495#comment-13190495 ] 

Andrea Del Bene commented on WICKET-4339:
-----------------------------------------

Hi Nick,

in the code you have attached ther's no clue of WiQuery. Your unit test seems to contains some errors, for example you refer to autocomplete with the id "ddc" and not with "roles".

However I've find a weird behaviour  of WiQuery which might a bug of this library. If I run the autocomplete example with wiquery in the classpath, the Wicket autocomplete won't work because jquery will be used instead of regular JavaScript code when component is initialize (i.e. '$(document).ready(function(event){new Wicket.AutoComplete' etc...).
Removing WiQuery jars everything works fine and regular JavaScript is used (i.e. 'Wicket.Event.add(window, "domready",' etc...).

See my quickstart for further details.
                
> Possible bug with 1.5 and WiQuery (might be a WiQuery problem)
> --------------------------------------------------------------
>
>                 Key: WICKET-4339
>                 URL: https://issues.apache.org/jira/browse/WICKET-4339
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.5.3
>            Reporter: Nick Pratt
>         Attachments: AutoCompleteProblem.tar.gz, autocomplete.zip
>
>
> See attached quickstart + unit tests.  Unsure if this is a Wicket or a WiQuery problem.

--
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-4339) Possible bug with 1.5 and WiQuery (might be a WiQuery problem)

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

Nick Pratt updated WICKET-4339:
-------------------------------

          Description: See attached quickstart + unit tests.  Unsure if this is a Wicket or a WiQuery problem.  (was: See attached quickstart + unit tests)
    Affects Version/s: 1.5.3
    
> Possible bug with 1.5 and WiQuery (might be a WiQuery problem)
> --------------------------------------------------------------
>
>                 Key: WICKET-4339
>                 URL: https://issues.apache.org/jira/browse/WICKET-4339
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.5.3
>            Reporter: Nick Pratt
>         Attachments: AutoCompleteProblem.tar.gz
>
>
> See attached quickstart + unit tests.  Unsure if this is a Wicket or a WiQuery problem.

--
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] [Commented] (WICKET-4339) Possible bug with 1.5 and WiQuery (might be a WiQuery problem)

Posted by "Nick Pratt (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187379#comment-13187379 ] 

Nick Pratt commented on WICKET-4339:
------------------------------------

Run the unit tests - the AutoCompleteTextField example works as expected. The one using WiQuery throws an exception.  Running the application with the WiQuery version works as expected (i.e. the model value is set on form submission).


                
> Possible bug with 1.5 and WiQuery (might be a WiQuery problem)
> --------------------------------------------------------------
>
>                 Key: WICKET-4339
>                 URL: https://issues.apache.org/jira/browse/WICKET-4339
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.5.3
>            Reporter: Nick Pratt
>         Attachments: AutoCompleteProblem.tar.gz
>
>
> See attached quickstart + unit tests.  Unsure if this is a Wicket or a WiQuery problem.

--
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