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 2011/09/23 22:15:26 UTC

[jira] [Resolved] (TAP5-802) Tapestry should report client-side initialization errors (using the console) but then continue as best it can

     [ https://issues.apache.org/jira/browse/TAP5-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship resolved TAP5-802.
---------------------------------------

    Resolution: Invalid
      Assignee: Howard M. Lewis Ship

Actually, fail-fast is much better. Ignored warnings are never fixed.

> Tapestry should report client-side initialization errors (using the console) but then continue as best it can
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-802
>                 URL: https://issues.apache.org/jira/browse/TAP5-802
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>
> Although there's something to be said for "fail fast", it would still be nice if the first initialization failure would not bring all client-side logic to a stop. Currently, if there's any problem with any initialization JavaScript, you end up with very incomplete client-side initialization.

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