Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.misc > #13224

Re: Web design, page cache (or what ever you call it).

From Michael Black <et472@ncf.ca>
Newsgroups comp.misc
Subject Re: Web design, page cache (or what ever you call it).
Date 2017-02-27 12:45 -0500
Organization National Capital Freenet, Ottawa, Ontario, Canada
Message-ID <alpine.LNX.2.02.1702271243550.6852@darkstar.example.org> (permalink)
References <ehi3t8Fci0lU1@mid.individual.net> <o910ah$js3$2@dont-email.me>

Show all headers | View raw


On Mon, 27 Feb 2017, Rich wrote:

> Larry Sheldon <lfsheldon@gmail.com> wrote:
>> WHY?  WHY!?  WHY!!????!??
>>
>> Why do page designers pollute the page cache (or what ever you call it)
>> so that when a person trying to do use do useful work and back out of a
>> dead end by using the "back arrow" button, the same page loads?
>
> Usually it is simple incompetence.
>
> This is often caused by using Javascript onclick handlers to do "links"
> (even though HTML has a perfectly good link tag in the <a> tag) and
> unless they also go to extra effort to update the back button records
> from the javascript code, you get a broken back button.
>
> But the "cache" has nothing to do with it.  The back button is not a
> "go back in the cache" button.  It is just a list of all the past URL
> links you clicked upon in that tab/window.
>
>> I am abut to declare such pages to be malway and block them.
>
> They are, and skipping them is often the only recourse, given that many
> have no one competent creating them in the first place.
>
>
I've yet to find one of value.  One reason you notice the back button 
isn't working is because you realize you aren't interested, and try to get 
back from where you came.

If it was an interesting page, you might get lost in the content, and then 
when you want to move on, just move to another site.  But when the content 
is bad, the immediate reaction is to go back to where you came, after all, 
you were only curious about the site.

   Michael

Back to comp.misc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Web design, page cache (or what ever you call it). Larry Sheldon <lfsheldon@gmail.com> - 2017-02-27 01:47 -0600
  Re: Web design, page cache (or what ever you call it). Kees Nuyt <k.nuyt@nospam.demon.nl> - 2017-02-27 10:48 +0100
    Re: Web design, page cache (or what ever you call it). Jerry Peters <jerry@example.invalid> - 2017-02-27 21:08 +0000
  Re: Web design, page cache (or what ever you call it). Whiskers <catwheezel@operamail.com> - 2017-02-27 09:49 +0000
  Re: Web design, page cache (or what ever you call it). Rich <rich@example.invalid> - 2017-02-27 10:50 +0000
    Re: Web design, page cache (or what ever you call it). Michael Black <et472@ncf.ca> - 2017-02-27 12:45 -0500
      Re: Web design, page cache (or what ever you call it). Larry Sheldon <lfsheldon@gmail.com> - 2017-02-27 20:29 -0600
        Re: Web design, page cache (or what ever you call it). Rich <rich@example.invalid> - 2017-02-28 03:34 +0000
          Re: Web design, page cache (or what ever you call it). Pham Nuwen <phamnuwen@example.com> - 2017-02-28 08:41 -0800
            Re: Web design, page cache (or what ever you call it). Kara M'bola <maxupixu@in.val.it> - 2017-03-03 21:55 +0000
              Re: Web design, page cache (or what ever you call it). Johnny B Good <johnny-b-good@invalid.ntlworld.com> - 2017-03-14 16:49 +0000
    Re: Web design, page cache (or what ever you call it). Kerry Imming <kcimming@pobox.com> - 2017-03-16 12:00 -0500
      Re: Web design, page cache (or what ever you call it). Rich <rich@example.invalid> - 2017-03-16 18:09 +0000
        Re: Web design, page cache (or what ever you call it). Kerry Imming <kcimming@pobox.com> - 2017-03-16 13:53 -0500
          Re: Web design, page cache (or what ever you call it). Rich <rich@example.invalid> - 2017-03-16 18:58 +0000

csiph-web