Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | Rich <rich@example.invalid> |
|---|---|
| Newsgroups | comp.misc |
| Subject | Re: Web design, page cache (or what ever you call it). |
| Date | 2017-03-16 18:09 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <oaekc8$vlo$2@dont-email.me> (permalink) |
| References | <ehi3t8Fci0lU1@mid.individual.net> <o910ah$js3$2@dont-email.me> <oaeg56$jdu$1@dont-email.me> |
Kerry Imming <kcimming@pobox.com> wrote: > On 2/27/2017 4:50 AM, Rich wrote: >> >> 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. >> > > If you go to CNET's news.com site in Firefox and click on an article, > you get an entry in your "Back" buffer as expected. What I DON'T > expect is to get additional links in the back buffer as I scroll down > the page (which does happen). In other words, I expect the back > button to take me to the last link I CLICKED. > > In my opinion this new behavior is wrong if for no other reason than > it's inconsistent among web sites. That would be a new 'mis-feature' where they are abusing the javascript API that allows manipulation of the "back button list" to stuff it with things you never actually clicked upon. That's a sneaky way to increase page views on the unsuspecting, because when you 'back out' and go to a different page they see it as a fresh retreival. This is probably the next variant on the "unnecessarially split an article up into 10 chunks to increase my page views and number of 'ad impressions'" method that way too many sites also use.
Back to comp.misc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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