> I created jira TAP5-2279
Thanks for your help! It will be a useful fix.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
I created jira TAP5-2279
On 30 Jan 2014 09:30, "Lance Java" wrote:
> It sounds like the browser is trying to be smart. Please file a jira.
>
> I guess we need some clientside logic to refresh the page if the URL is
> the same.
>
It sounds like the browser is trying to be smart. Please file a jira.
I guess we need some clientside logic to refresh the page if the URL is the
same.
On 30 янв. 2014 г., at 11:59, Lance Java wrote:
> I wonder if this is a browser 'feature' (ie only refresh if the URL changes
> from current)
>
> Do you see this behaviour in all browsers?
Same behavior on Chrome, Firefox, Opera on Ubuntu and Safari on Mac OS X.
Well, it seems like browser be
> but I'd also call that a very confusing naming of pages.
Agreed! I'd say a possible 'fix' would be for Tapestry to throw exception
when it encounters the two ambiguous pages at startup.
FYI I'm assuming Tapestry does something like
window.location.href = redirectURL
On 30 Jan 2014 07:59, "Lance Java" wrote:
> Hmm... Looks good to me.
>
> I wonder if this is a browser 'feature' (ie only refresh if the URL
> changes from current)
>
> Do you see this behaviour in all browsers?
>
Hmm... Looks good to me.
I wonder if this is a browser 'feature' (ie only refresh if the URL changes
from current)
Do you see this behaviour in all browsers?
On 30 Jan 2014 07:27, "Oleg Gulyaev" wrote:
> Yes, I found it, here it is:
>
> {
> "redirectURL" : "/comments/52e9f9e5e4b0ba0bb02
