viewing CSS

2013-02-18 Thread John Rickman Iyonix
Does anyone know of a neater way of viewing CSS? What I do at present is press F8 to view html. look at the -http://rickman.orpheusweb.co.uk/lynx

Re: viewing CSS

2013-02-18 Thread Brian Jordan
In message <0229de1f53.iyoj...@rickman.argonet.co.uk> John Rickman Iyonix wrote: > Does anyone know of a neater way of viewing CSS? [snip] Full save to disc, open generated pseudo app, read CSS file(s). Or have I missed the point? -- Brian Jordan Virtual RPC-AdjustSA on Windows 8

Re: viewing CSS

2013-02-18 Thread Tim Hill
In article <0229de1f53.iyoj...@rickman.argonet.co.uk>, John Rickman Iyonix wrote: > Does anyone know of a neater way of viewing CSS? > What I do at present is > press F8 to view html. > look at the - click in the NS url text area > delete back to the url base > type the CSS relative p

Re: viewing CSS

2013-02-18 Thread Rob Kendrick
On Mon, Feb 18, 2013 at 10:23:46AM +, Tim Hill wrote: > > It would be useful if NetSurf had a View CSS.. menu option, but I have > > no idea how much work this would involve. > > More than very occasional use by a very few of us would warrant, I > imagine. Given a web page can have basically

Re: viewing CSS

2013-02-18 Thread John Rickman Iyonix
Rob Kendrick wrote > On Mon, Feb 18, 2013 at 10:23:46AM +, Tim Hill wrote: >>> It would be useful if NetSurf had a View CSS.. menu option, but I have >>> no idea how much work this would involve. >> >> More than very occasional use by a very few of us would warrant, I >> imagine. > Given a

NetSurf html events

2013-02-18 Thread John Rickman Iyonix
Are any of the html mouse events working in NetSurf? eg click, mouseover, mouseout, mousemove. The final item on the page for the link below, "mouse event tests" works on Firefox but not on NestSurf. http://rickman.orpheusweb.co.uk/testing/index.html Is there any more detailed documentation

Latest builds crash when opening hotlist/history pages

2013-02-18 Thread Harriet Bazley
Builds json-904 and json-904 both crash when I double-click on a hotlist or browsing history entry with a stack backtrace along the following lines: Stack backtrace: Running thread 0x622968 ( 62bee4) pc: 489178 lr:abf44 sp: 62bee8 __write_backtrace() ( 62bf10) pc:abec8 lr: 48