You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/07/31 10:53:15 UTC

[jira] Created: (TAP5-800) Server side error during provideCompletions event for Autocompleter mixin is not reported on the client side properly

Server side error during provideCompletions event for Autocompleter mixin is not reported on the client side properly
---------------------------------------------------------------------------------------------------------------------

                 Key: TAP5-800
                 URL: https://issues.apache.org/jira/browse/TAP5-800
             Project: Tapestry 5
          Issue Type: Bug
          Components: tapestry-core
    Affects Versions: 5.1.0.5
            Reporter: Howard M. Lewis Ship


You would expect that the console would be raised to display the Ajax error (as happens with, say, a Zone update) but instead you get no notification and some wierd presentation oddities (I believe because the autocompleter is expecting an <UL> markup snippet, and instead recieves the exception report page!).

It may just be time to find a complete replacement for the Scriptaculous.Autocompleter.

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


[jira] Updated: (TAP5-800) Server side error during provideCompletions event for Autocompleter mixin is not reported on the client side properly

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-800:
--------------------------------------

    Priority: Minor  (was: Major)

> Server side error during provideCompletions event for Autocompleter mixin is not reported on the client side properly
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-800
>                 URL: https://issues.apache.org/jira/browse/TAP5-800
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Howard M. Lewis Ship
>            Priority: Minor
>
> You would expect that the console would be raised to display the Ajax error (as happens with, say, a Zone update) but instead you get no notification and some wierd presentation oddities (I believe because the autocompleter is expecting an <UL> markup snippet, and instead recieves the exception report page!).
> It may just be time to find a complete replacement for the Scriptaculous.Autocompleter.

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


[jira] Updated: (TAP5-800) Server side error during provideCompletions event for Autocompleter mixin is not reported on the client side properly

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-800:
--------------------------------------

    Priority: Minor  (was: Major)

> Server side error during provideCompletions event for Autocompleter mixin is not reported on the client side properly
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-800
>                 URL: https://issues.apache.org/jira/browse/TAP5-800
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Howard M. Lewis Ship
>            Priority: Minor
>
> You would expect that the console would be raised to display the Ajax error (as happens with, say, a Zone update) but instead you get no notification and some wierd presentation oddities (I believe because the autocompleter is expecting an <UL> markup snippet, and instead recieves the exception report page!).
> It may just be time to find a complete replacement for the Scriptaculous.Autocompleter.

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