|
Posted by Neredbojias on 10/20/07 03:01
Well bust mah britches and call me cheeky, on Fri, 19 Oct 2007 15:50:00
GMT Tim Streater scribed:
>> > In fact, if I had my way, I'd prevent any of these going into the
>> > history stack.
>>
>> JavaScript should be able do that, for those who have it enabled.
>
> Interesting. When I looked into this, the docs I looked at seemed to
> be quite clear that there was no way to prevent a page going into the
> history stack, and that this was deliberate.
This isn't true at all. Location.replace() replaces a page without adding
a slot to the history. Perhaps the docs you mention were once correct but
not updated when updating would have been manifestly prudent...
--
Neredbojias
[Back to original message]
|