On 2 Jun 2014 David Pitt <pittdj@pittdj.co.uk> wrote:
> Harriet Bazley, on 2 Jun, wrote:
>> Of recent weeks I've increasingly found that Google searches are not
>> rendering in Netsurf, especially when you try to view a second or
>> subsequent page of search results: the window just hangs there with the
>> progress indicator moving instead of the usual almost instant return.
>> Clicking on the same link again to force another fetch seems to be the
>> only way to get the results.
>>
>> Is anyone else seeing this, or is it my ISP?
>>
>> (Netsurf v1932, JS disabled)
>>
> A quick test did reproduce this, v1920, Java Script not disabled, adverts
> hidden. Plusnet.
Has anyone reported this to he bug site? If nobody else does I'll do
it later today.
Best wishes,
Peter.
--
Peter Young (zfc W) and family
Prestbury, Cheltenham, Glos. GL52, England
http://pnyoung.orpheusweb.co.uk
pnyoung@ormail.co.uk
Monday, 2 June 2014
Re: Google hanging
Harriet Bazley, on 2 Jun, wrote:
> Of recent weeks I've increasingly found that Google searches are not
> rendering in Netsurf, especially when you try to view a second or
> subsequent page of search results: the window just hangs there with the
> progress indicator moving instead of the usual almost instant return.
> Clicking on the same link again to force another fetch seems to be the
> only way to get the results.
>
> Is anyone else seeing this, or is it my ISP?
>
> (Netsurf v1932, JS disabled)
>
A quick test did reproduce this, v1920, Java Script not disabled, adverts
hidden. Plusnet.
--
David Pitt
> Of recent weeks I've increasingly found that Google searches are not
> rendering in Netsurf, especially when you try to view a second or
> subsequent page of search results: the window just hangs there with the
> progress indicator moving instead of the usual almost instant return.
> Clicking on the same link again to force another fetch seems to be the
> only way to get the results.
>
> Is anyone else seeing this, or is it my ISP?
>
> (Netsurf v1932, JS disabled)
>
A quick test did reproduce this, v1920, Java Script not disabled, adverts
hidden. Plusnet.
--
David Pitt
Re: Google hanging
In message <7f015b1154.harriet@blueyonder.co.uk>
Harriet Bazley <lists@orange.wingsandbeaks.org.uk> wrote:
>Of recent weeks I've increasingly found that Google searches are not
>rendering in Netsurf, especially when you try to view a second or
>subsequent page of search results: the window just hangs there with the
>progress indicator moving instead of the usual almost instant return.
>Clicking on the same link again to force another fetch seems to be the
>only way to get the results.
>
>Is anyone else seeing this, or is it my ISP?
>
>(Netsurf v1932, JS disabled)
>
Yes, I have seen this for a while now. An annoying little trait.
It was suggested that switching off JS might help. It doesn't or at
best only marginally. (Currently Netsurf v1930, JS disabled). My ISP is
demon but I doubt this is the problem.
Regards,
--
Graham Pickles
www.whitbymuseum.org.uk Whitby Museum
A little inaccuracy sometimes saves tons of explanation. (Saki)
Harriet Bazley <lists@orange.wingsandbeaks.org.uk> wrote:
>Of recent weeks I've increasingly found that Google searches are not
>rendering in Netsurf, especially when you try to view a second or
>subsequent page of search results: the window just hangs there with the
>progress indicator moving instead of the usual almost instant return.
>Clicking on the same link again to force another fetch seems to be the
>only way to get the results.
>
>Is anyone else seeing this, or is it my ISP?
>
>(Netsurf v1932, JS disabled)
>
Yes, I have seen this for a while now. An annoying little trait.
It was suggested that switching off JS might help. It doesn't or at
best only marginally. (Currently Netsurf v1930, JS disabled). My ISP is
demon but I doubt this is the problem.
Regards,
--
Graham Pickles
www.whitbymuseum.org.uk Whitby Museum
A little inaccuracy sometimes saves tons of explanation. (Saki)
Re: Google hanging
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I've noticed the same, thought it was just me
Cheers
Malcolm
On Jun 2, 2014, Harriet Bazley <lists@orange.wingsandbeaks.org.uk> wrote:
>Of recent weeks I've increasingly found that Google searches are not
>rendering in Netsurf, especially when you try to view a second or
>subsequent page of search results: the window just hangs there with the
>progress indicator moving instead of the usual almost instant return.
>Clicking on the same link again to force another fetch seems to be the
>only way to get the results.
>
>Is anyone else seeing this, or is it my ISP?
>
>(Netsurf v1932, JS disabled)
- -- Sent with K-@ Mail - the evolution of emailing.
-----BEGIN PGP SIGNATURE-----
Version: APG v1.1.1
iQJPBAEBCgA5BQJTjC/FMhxNYWxjb2xtIEh1c3NhaW4tR2FtYmxlcyA8bWFsY29s
bUBwYXltZW50bGFicy5jb20+AAoJEJMie8gvUzDPL5kQAMAtgM484ky3FbQFUym5
KPueCF0sthxuNy1deqpwHQx9yXy/QXGIlKhoZxiXRkBLXjh9RA55LHcr+vC74g4Q
zotFShz5UsNsTsjNQH346AS69n3qXuWfN9zfnBCbWyUuR/vgIunW3p8TAhqkznki
tGIlz4p1w1aOSTYJYIz5baH3Nk0ZUTErQZ498YqxiDDwFfdd82AA8CnKNNBPZb+K
j0DDn3RBNVYjliom+xafcOkLyE2ByU5UIG+e/LWnjZxjgm9huOXwA/8nVzI7Ehie
kfAvJlXq/qVu6eh3UFAdvcOqV/055p6T54NFFMdVQr3r0t+048I1/ubYBH8cDdjM
j0G8LxL8kFQ4fAChe5/NwmkdBVu3FVFkt+qClarVx6+xZhuyH2Kx//6nHvE4yCUt
s2HyupipCKdPHnARzXoJ22+wkRTLCdhHgbbUtL2MhI4sorJtgYfBq6wNvR9IlukM
fmQE713ND0uKLFDhCvCt4aHsvdNixvtdIquR7o3hL13Pb/Woj/IOybgNBjBe8bgQ
1MrpEAf/30EcfY9jBFnS3XggMyNdqPsFR40HqnwmYySIBpyTjHfsvKnRlkAYmPNP
b5pmYMtAAAh8wBYeLRfLT3z7/HG07+OwbEC2OTVsAdo3X9Wt28yccvooIPCIrke2
VZEPqmxT/7CXWE5tfqIIv26y
=w0e4
-----END PGP SIGNATURE-----
Hash: SHA512
I've noticed the same, thought it was just me
Cheers
Malcolm
On Jun 2, 2014, Harriet Bazley <lists@orange.wingsandbeaks.org.uk> wrote:
>Of recent weeks I've increasingly found that Google searches are not
>rendering in Netsurf, especially when you try to view a second or
>subsequent page of search results: the window just hangs there with the
>progress indicator moving instead of the usual almost instant return.
>Clicking on the same link again to force another fetch seems to be the
>only way to get the results.
>
>Is anyone else seeing this, or is it my ISP?
>
>(Netsurf v1932, JS disabled)
- -- Sent with K-@ Mail - the evolution of emailing.
-----BEGIN PGP SIGNATURE-----
Version: APG v1.1.1
iQJPBAEBCgA5BQJTjC/FMhxNYWxjb2xtIEh1c3NhaW4tR2FtYmxlcyA8bWFsY29s
bUBwYXltZW50bGFicy5jb20+AAoJEJMie8gvUzDPL5kQAMAtgM484ky3FbQFUym5
KPueCF0sthxuNy1deqpwHQx9yXy/QXGIlKhoZxiXRkBLXjh9RA55LHcr+vC74g4Q
zotFShz5UsNsTsjNQH346AS69n3qXuWfN9zfnBCbWyUuR/vgIunW3p8TAhqkznki
tGIlz4p1w1aOSTYJYIz5baH3Nk0ZUTErQZ498YqxiDDwFfdd82AA8CnKNNBPZb+K
j0DDn3RBNVYjliom+xafcOkLyE2ByU5UIG+e/LWnjZxjgm9huOXwA/8nVzI7Ehie
kfAvJlXq/qVu6eh3UFAdvcOqV/055p6T54NFFMdVQr3r0t+048I1/ubYBH8cDdjM
j0G8LxL8kFQ4fAChe5/NwmkdBVu3FVFkt+qClarVx6+xZhuyH2Kx//6nHvE4yCUt
s2HyupipCKdPHnARzXoJ22+wkRTLCdhHgbbUtL2MhI4sorJtgYfBq6wNvR9IlukM
fmQE713ND0uKLFDhCvCt4aHsvdNixvtdIquR7o3hL13Pb/Woj/IOybgNBjBe8bgQ
1MrpEAf/30EcfY9jBFnS3XggMyNdqPsFR40HqnwmYySIBpyTjHfsvKnRlkAYmPNP
b5pmYMtAAAh8wBYeLRfLT3z7/HG07+OwbEC2OTVsAdo3X9Wt28yccvooIPCIrke2
VZEPqmxT/7CXWE5tfqIIv26y
=w0e4
-----END PGP SIGNATURE-----
Re: Google hanging
In article <7f015b1154.harriet@blueyonder.co.uk>,
Harriet Bazley <lists@orange.wingsandbeaks.org.uk> wrote:
> Is anyone else seeing this, or is it my ISP?
> (Netsurf v1932, JS disabled)
I was experiencing it yesterday with 1929/1930, JS disabled. Plusnet.
Thought it was just me!
John
--
| John Williams
| johnrw@ukgateway.net
Names for Soul Band:- The Soul Criterion *
Harriet Bazley <lists@orange.wingsandbeaks.org.uk> wrote:
> Is anyone else seeing this, or is it my ISP?
> (Netsurf v1932, JS disabled)
I was experiencing it yesterday with 1929/1930, JS disabled. Plusnet.
Thought it was just me!
John
--
| John Williams
| johnrw@ukgateway.net
Names for Soul Band:- The Soul Criterion *
Google hanging
Of recent weeks I've increasingly found that Google searches are not
rendering in Netsurf, especially when you try to view a second or
subsequent page of search results: the window just hangs there with the
progress indicator moving instead of the usual almost instant return.
Clicking on the same link again to force another fetch seems to be the
only way to get the results.
Is anyone else seeing this, or is it my ISP?
(Netsurf v1932, JS disabled)
--
Harriet Bazley == Loyaulte me lie ==
Money is the root of all evil - and man needs roots
rendering in Netsurf, especially when you try to view a second or
subsequent page of search results: the window just hangs there with the
progress indicator moving instead of the usual almost instant return.
Clicking on the same link again to force another fetch seems to be the
only way to get the results.
Is anyone else seeing this, or is it my ISP?
(Netsurf v1932, JS disabled)
--
Harriet Bazley == Loyaulte me lie ==
Money is the root of all evil - and man needs roots
Sunday, 1 June 2014
Re: Amiga nsfont_split
On Sun, 18 May 2014 23:07:26 +0100, Michael Drake wrote:
> Well anyway, the first and last state of the log you provided were
> identical. Splitting 132 chars ("No it's not. It's licensed nationally
> for the transmitters specified in the licence. It's the same multiplex
> all over the country."), at 550px. The first time it split at 100
> chars, and the second time at 110.
It seems the problem was that the conversion to UTF-16 was randomly
inserting a BOM at the start of the string. When it was present, the
string characters were all pushed along by one (and probably never
checked the last character), and the first character was always size
0.
The extra character must have affected the number of characters
NetSurf thought it could fit in the space, even though it was zero
width. Anyway, I'm confident this is fixed now.
Chris
> Well anyway, the first and last state of the log you provided were
> identical. Splitting 132 chars ("No it's not. It's licensed nationally
> for the transmitters specified in the licence. It's the same multiplex
> all over the country."), at 550px. The first time it split at 100
> chars, and the second time at 110.
It seems the problem was that the conversion to UTF-16 was randomly
inserting a BOM at the start of the string. When it was present, the
string characters were all pushed along by one (and probably never
checked the last character), and the first character was always size
0.
The extra character must have affected the number of characters
NetSurf thought it could fit in the space, even though it was zero
width. Anyway, I'm confident this is fixed now.
Chris
Subscribe to:
Posts (Atom)