2:02 p.m.
3.10 (Dev CI #5055)
Couple of issues I've noticed recently:
- Wikipedia's own vertical scroll bar overrides the functionality of the
RISC OS window furniture. Is that intentional and/or inevitable?
- F4 / Find text no longer automatically scrolls down to display the next
occurrence of the search string when it is further down the text than is
visible in the current window.
If others concur, I could raise a bug report, at least for the latter.
--
Bernard
3:16 p.m.
On 6 Apr 2020 Bernard Boase <b.boase(a)bcs.org> wrote:
3.10 (Dev CI #5055)
Couple of issues I've noticed recently:
- Wikipedia's own vertical scroll bar overrides the functionality
of the
RISC OS window furniture. Is that intentional and/or inevitable?
- F4 / Find text no longer automatically scrolls down to display the
next
occurrence of the search string when it is further down the text than is
visible in the current window.
If others concur, I could raise a bug report, at least for the
latter.
I concur.
Best wishes,
Peter.
--
Peter Young (zfc Hg) and family
Prestbury, Cheltenham, Glos. GL52, England
http://pnyoung.orpheusweb.co.uk
pnyoung(a)ormail.co.uk
4:26 p.m.
In article <712aea5c58.boase(a)boase.myzen.co.uk>,
Bernard Boase <b.boase(a)bcs.org> wrote:
- Wikipedia's own vertical scroll bar overrides the
functionality
of the RISC OS window furniture. Is that intentional and/or
inevitable?
Yes - that has annoyed me for a while now.
--
Chris Johnson
Edinburgh
6:17 p.m.
On 6 Apr, cj wrote in message
<585cf76494chris(a)chris-johnson.org.uk>:
In article <712aea5c58.boase(a)boase.myzen.co.uk>,
Bernard Boase <b.boase(a)bcs.org> wrote:
> - Wikipedia's own vertical scroll bar overrides the functionality of the
> RISC OS window furniture. Is that intentional and/or inevitable?
Yes - that has annoyed me for a while now.
Feel free to fix it... :-)
The issue is that NetSurf's core has to render any frame furniture when a
page requests it be drawn, and whilst it defers this to the GUI (IIRC), it's
fairly non-trivial for the RISC OS front-end to use the standard desktop
furniture.
It's been a long time, but (again IIRC) I'm fairly sure that I concluded
when I looked at this that the only way to get "standard" scrollbars would
be to replicate the Wimp's rendering of the component bits within NetSurf's
RISC OS front-end -- which, aside from being relatively complex, also took
us into areas best described as "sparsely documented" and hence fragile if
the OS developers change the way things work.
--
Steve Fryatt - Leeds, England
http://www.stevefryatt.org.uk/
6:28 p.m.
In message <712aea5c58.boase(a)boase.myzen.co.uk>
Bernard Boase <b.boase(a)bcs.org> wrote:
Couple of issues I've noticed recently:
Me too!
- Wikipedia's own vertical scroll bar overrides the functionality
of the
RISC OS window furniture. Is that intentional and/or inevitable?
It's like the whole page is in a frame :-O Scrolling feels slower and
jerkier too.
- F4 / Find text no longer automatically scrolls down to display the
next
occurrence of the search string when it is further down the text than is
visible in the current window.
That is only true within one of these odd scrolling pages. Search
still auto scrolls to the found text in other web pages.
3.10 (Dev CI #5055)
I'm on 5053 but also tried 4953 and with 3.9 and 3.8, all the same.
I don't remember it doing that before (I think!) so is this something
that Wikipedia have changed in their page layout?
If others concur, I could raise a bug report, at least for the
latter.
Looking at The Register that also has a NetSurf internal scrollbar,
but his time it is stuck a full size and the normal RISC OS scrollbar
works. Weird.
Bryan.
--
RISC OS User Group Of London - http://www.rougol.jellybaby.net/
RISC OS London Show - http://www.riscoslondonshow.co.uk/
10:47 p.m.
In article <mpro.q8dh4m04f6znk02bd.lists(a)stevefryatt.org.uk>, Steve
Fryatt <lists(a)stevefryatt.org.uk> wrote:
The issue is that NetSurf's core has to render any frame
furniture when
a page requests it be drawn, and whilst it defers this to the GUI
(IIRC), it's fairly non-trivial for the RISC OS front-end to use the
standard desktop furniture.
It's been a long time, but (again IIRC) I'm fairly sure that
I
concluded when I looked at this that the only way to get "standard"
scrollbars would be to replicate the Wimp's rendering of the component
bits within NetSurf's RISC OS front-end -- which, aside from being
relatively complex, also took us into areas best described as "sparsely
documented" and hence fragile if the OS developers change the way
things work.
I just had a quick peek inside the RISC OS Wikipedia page. There is no
FRAME or IFRAME but it has the extra scrollbar. Its stylesheet defines
the BODY with 'overflow-y:scroll'. Any browser with window furniture
already in place should have that set on BODY by default, shouldn't it,
and ignore if it's set there again? Just a thought.
NetSurf also seems to ignore the principle of what overflow means (I.e.
'*if* the content overflows, do this') though that's less crucial.
<html><head><title>Test overflow-y:scroll</title></head>
<body style="overflow-y:scroll">
Hello World <br>
Hello World <br>
Hello World <br>
</body></html>
Unfortunately, it is also an inherited property as this short HTML page
demonstrates! Use it with care please Jimmy!
T
--
Tim Hill
--------
Find an event to attend at:
http://timil.com/riscos/calendar/
Mimemap and other stuff:
http://timil.com/riscos/
12:37 a.m.
In message <585d1a4b61tim(a)timil.com>
Tim Hill <tim(a)timil.com> wrote:
In article <mpro.q8dh4m04f6znk02bd.lists(a)stevefryatt.org.uk>,
Steve Fryatt
<lists(a)stevefryatt.org.uk> wrote:
> The issue is that NetSurf's core has to render any frame furniture when a
> page requests it be drawn, and whilst it defers this to the GUI (IIRC),
> it's fairly non-trivial for the RISC OS front-end to use the standard
> desktop furniture.
> It's been a long time, but (again IIRC) I'm fairly sure that I concluded
> when I looked at this that the only way to get "standard" scrollbars
> would be to replicate the Wimp's rendering of the component bits within
> NetSurf's RISC OS front-end -- which, aside from being relatively
> complex, also took us into areas best described as "sparsely documented"
> and hence fragile if the OS developers change the way things work.
I just had a quick peek inside the RISC OS Wikipedia page. There is no
FRAME or IFRAME but it has the extra scrollbar. Its stylesheet defines the
BODY with 'overflow-y:scroll'. Any browser with window furniture already in
place should have that set on BODY by default, shouldn't it, and ignore if
it's set there again? Just a thought.
Interesting. Thanks for investigating the cause, Tim.
I just visited the RISC OS Wikipedia page with NetSurf and did a Full
Save, then looked for occurrences of "overflow-y". There is just one.
I set its value to "visible". Double-clicking the app then rendered
the page with only the normal RISC OS scroll bars, which of course
allowed quick and smooth scrolling in the way one would expect.
So perhaps we should turn this on its head and ask if there is any
situation where this result would not be the best.
David
237
days inactive
237
days old
netsurf-users@netsurf-browser.org
6 comments
7 participants
participants (7)
-
Bernard Boase -
Bryan Hogan -
cj -
David Higton -
Peter Young -
Steve Fryatt -
Tim Hill