|
|
Posted by Jake on 10/07/05 18:33
In message <1ucbllxy0c5yq$.1m6n1dnppp8r.dlg@40tude.net>, Beauregard T.
Shagnasty <a.nony.mous@example.invalid> writes
>Jake wrote:
>
>> In message <1bs7jtot208wr$.1dmpqzozm7es8.dlg@40tude.net>, rf
>> <rf@invalid.com> writes
>>> Jake wrote:
>>>
>>> [opening new window]
>>>
>>>> Ever been to a site which, with badly-tested flash and/or
>>>> javascript, prevents the back-button from ever working?
>>>
>>> And what does your solution do? Breaks the back button.
>>
>> You've lost me there, I'm afraid.
>>
>> As you've opened the page in a new window -- how is the back button
>> relevant?
>
>The new window has nothing in the history, so clicking the back button
>does nothing.
Yes.
>Ergo, it is broken.
No. Simply not relevant in this context. If you have no history, the
back button has no function.
>
>> Anyway, as I've said -- much easier to kill a window than to reload
>> the browser.
>
>Aha, here's the realization. If your browser was maximized, and a page
>opened in a new maximized window on top of it, how would you know it
>*was* a new window?
(A) visual - 'cos that's what the message tells me. What message? The
message on the page that says "link opens in a new window" -- or
equivalent.
(B) audio/visual - as above, plus an audio tone.
>And it has a broken back button... So, what do you
>do? You go back to Google and pick another site. Sometime later in the
>day, when you are finished surfing, you close this "new" window and you
>find that original window still there... but long since forgotten.
When I've finished, I kill the window. If the original is there, I kill
that one too. What's so difficult about that?
Regards.
>
--
Jake (jake@gododdin.demon.co.uk -- just a 'spam trap' mail address)
Navigation:
[Reply to this message]
|