[
https://issues.apache.org/jira/browse/TAPESTRY-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572369#action_12572369
]
Ernest Monklitch commented on TAPESTRY-2159:
--------------------------------------------
Have seen same behavior, the js _should_ be updated by the browser but it
isn't. I don't know how Jesse solved this issue, but sometimes when browsers
have old version in local cache it can cause all sorts of problems. And, after
that the support center gets angry calls, which in turn increases negative
attitude towards the software amongst other bad things....
The different-url-per-version approach is the only that works for sure afaik.
I would estimate that the priority of this is quite low, but should be kept in
the list. (Just my opinion, you may disagree ;) )
> Version bundled javascript
> --------------------------
>
> Key: TAPESTRY-2159
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2159
> Project: Tapestry
> Issue Type: Improvement
> Affects Versions: 5.0.10
> Environment: Any
> Reporter: Ernest Monklitch
> Fix For: 5.1
>
>
> Jesse Kuhnert has already implemented this in T4. (Jira issue TAPESTRY-2122.)
> Prevents client side errors that occur if user doesn't flush browser's cache
> between Tapestry upgrades. (And javascript has changed.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
