Re: BBC News websites

2013-01-15 Thread Chris Young
On Tue, 15 Jan 2013 21:12:32 + (GMT), Michael Drake wrote:

> > I'm not sure I necessarily agree with this workaround - a website
> > deciding that everything running ARM must want the mobile version of a
> > page is making a pretty big assumption
> 
> I decided there was no good reason for leaking processor architecture
> information anyway.

Some sites use it to determine the correct download to offer.  For
example, www.opera.com.  Under Linux, if you artificially add "; ppc"
where the processor information used to be, the download page will
give the Linux PowerPC version instead of the Linux x86 one.

Chris



Re: BBC News websites

2013-01-15 Thread Michael Drake
In article
,
   Chris Young  wrote:

> I'm not sure I necessarily agree with this workaround - a website
> deciding that everything running ARM must want the mobile version of a
> page is making a pretty big assumption

I decided there was no good reason for leaking processor architecture
information anyway.

-- 

Michael Drake (tlsa)  http://www.netsurf-browser.org/



Re: BBC News websites

2013-01-15 Thread Chris Young
On Tue, 15 Jan 2013 20:13:04 + (GMT), David H Wild wrote:

> I see that we now have normal access to the BBC news websites. Whether this
> is something done by the Netsurf team or someone at the BBC taking note of
> complaints I am pleased to see it happen.

Build #812 removed the processor from the user-agent string.

I'm not sure I necessarily agree with this workaround - a website
deciding that everything running ARM must want the mobile version of a
page is making a pretty big assumption - but it's better than being
redirected to the mobile versions of sites in perpetuity.

Chris



Re: BBC News websites

2013-01-15 Thread Martin Bazley
The following bytes were arranged on 15 Jan 2013 by David H Wild :

> I see that we now have normal access to the BBC news websites. Whether this
> is something done by the Netsurf team or someone at the BBC taking note of
> complaints I am pleased to see it happen.

It's something NetSurf did.  It no longer includes the CPU architecture
in the User-Agent string, because some cretin at the BBC decided that
the only web browsers running on ARM computers were those running on
mobile phones.

-- 
  __<^>__   "Start off every day with a smile and get it over with."
 / _   _ \  - W.C. Fields
( ( |_| ) )
 \_>   <_/  === Martin Bazley ==



Re: BBC News websites

2013-01-15 Thread Richard Porter
On 15 Jan 2013 David H Wild  wrote:

> I see that we now have normal access to the BBC news websites. Whether this
> is something done by the Netsurf team or someone at the BBC taking note of
> complaints I am pleased to see it happen.

I raised it as a technical problem twice, then as a complaint, and 
after they sent me an automatic response after ten days because they 
couldn't meet the target for replying I complained again. Looks like a 
few others did too! I still haven't had a reply.

-- 
Richard Porterhttp://www.minijem.plus.com/
  mailto:r...@minijem.plus.com
I don't want a "user experience" - I just want stuff that works.



BBC News websites

2013-01-15 Thread David H Wild
I see that we now have normal access to the BBC news websites. Whether this
is something done by the Netsurf team or someone at the BBC taking note of
complaints I am pleased to see it happen.

-- 
David Wild using RISC OS on broadband
www.davidhwild.me.uk



Re: Controlling Javascript -- button suggestion

2013-01-15 Thread Tony Moore
On 15 Jan 2013, Tim Hill  wrote:
> In article , Tony
> Moore  wrote:
> > On 14 Jan 2013, Tim Hill  wrote:
> > > In article <89e6ff0d53.c.n@virgin.net>, ChrisF
> > >  wrote:
> > > > In message <2f9bf20d53@nails.abbeypress.net> Jim Nagel
> > > >wrote:
>
> > [snip]
>
> > > > > A wee handy-feature suggestion (if it's not a lot of
> > > > > programming effort): A "Javascript on/off button" on the
> > > > > toolbar.
> > >
> > > > . like Webster has.
> > >
> > > . or a shortcut keypress which could be added to Buttonbar.
>
> > A menu option would be needed for ButtonBar, or Keystroke, to work.
>
> I don't know about Keystroke but that's not true for Buttonbar. If a
> keypress is understood by an application but not in its menu, it still
> works. Just tested it with PageUp/Down for NetSurf and they work but
> are not in the menu structure.

Sorry, I misunderstood your comment. Having read it more carefully, I
agree with you. (My NetSurf ButtonBar already has the same PageUp/Down.)

Tony






Re: Controlling Javascript -- button suggestion

2013-01-15 Thread Tim Hill
In article , Tony Moore
 wrote:
> On 14 Jan 2013, Tim Hill  wrote:
> > In article <89e6ff0d53.c.n@virgin.net>, ChrisF
> >  wrote:
> > > In message <2f9bf20d53@nails.abbeypress.net> Jim Nagel
> > >wrote:

> [snip]

> > > > A wee handy-feature suggestion (if it's not a lot of programming
> > > > effort): A "Javascript on/off button" on the toolbar.
> >
> > > . like Webster has.
> >
> > . or a shortcut keypress which could be added to Buttonbar.

> A menu option would be needed for ButtonBar, or Keystroke, to work.

I don't know about Keystroke but that's not true for Buttonbar. If a
keypress is understood by an application but not in its menu, it still
works. Just tested it with PageUp/Down for NetSurf and they work but are
not in the menu structure.

-- 
Tim Hill
..
www.timil.com