CSS position not supported workaround
I would like to be able to fix some heading content on a page so that when the page is scrolled the heading stays on the screen. Is there anyway to do this that would work in NetSurf? A JavaScript solution is obviously not on. It can be done with CSS but unfortunately NetSurf has not yet implemented the position:fixed property. The following web page works after a fashion on Chromium, but not on NetSurf. http://rickman.orpheusweb.co.uk/temp/position.html Helpful suggestions would bemuch appreciated. -- John - http://mug.riscos.org/
Re: CSS position not supported workaround
In article <970f2cef52.iyoj...@rickman.argonet.co.uk>, John Rickman Iyonix wrote: > I would like to be able to fix some heading content on a page so that > when the page is scrolled the heading stays on the screen. As you've seen position:fixed is not implemented. It is treated as position:absolute. Originally this was because there was no way to implement it in a way that would give satisfactory performance e.g. on peoples' RiscPCs. It forces a serious penalty on scrolling pages that use it. Same with background-attachment:fixed. Now we're less bothered about that, but we aren't likely to implement it before the layout engine rewrite. > Is there anyway to do this that would work in NetSurf? > A JavaScript solution is obviously not on. Only HTML Frames, but they have their own limitations. Does your design actually need it? Usually I detest it when I see it. :) The performance penalty can affect e.g. Chrome/Firefox on modern PCs too, although to a lesser extent. -- Michael Drake (tlsa) http://www.netsurf-browser.org/
Re: CSS position not supported workaround
Michael Drake wrote > In article <970f2cef52.iyoj...@rickman.argonet.co.uk>, >John Rickman Iyonix wrote: >> I would like to be able to fix some heading content on a page so that >> when the page is scrolled the heading stays on the screen. ... >> Is there anyway to do this that would work in NetSurf? >> A JavaScript solution is obviously not on. > Only HTML Frames, but they have their own limitations. > Does your design actually need it? Usually I detest it when I see it. :) > The performance penalty can affect e.g. Chrome/Firefox on modern PCs too, > although to a lesser extent. In this case, the design really does need it. What I want to keep at the top of the window is a lookup table which enables multiple interpretations of the content that follows. You can see what I am trying to do here:- http://rickman.orpheusweb.co.uk/john/songs/songsaf.html If you don't play the guitar it probably won't make a lot of sense, but basically it enables a guitarist to play any of the songs in any key without use of a capo. The performance hit on the scroll is acceptable here because once you have found the song you want to play you don't have to scroll again until you want to change songs. -- John - http://mug.riscos.org/
Re: CSS position not supported workaround
On Thu, 15 Nov 2012 22:03:15 GMT, John Rickman Iyonix wrote: > > Does your design actually need it? Usually I detest it when I see it. :) > > The performance penalty can affect e.g. Chrome/Firefox on modern PCs too, > > although to a lesser extent. > > In this case, the design really does need it. What I want to keep at > the top of the window is a lookup table which enables multiple > interpretations of the content that follows. > > You can see what I am trying to do here:- > > http://rickman.orpheusweb.co.uk/john/songs/songsaf.html > > If you don't play the guitar it probably won't make a lot of sense, > but basically it enables a guitarist to play any of the songs in any > key without use of a capo. > > The performance hit on the scroll is acceptable here because once you > have found the song you want to play you don't have to scroll again > until you want to change songs. I would have opted for a server-side PHP script which shows the bit that you want to keep static and the selected song only. Not only would that solve the problem, it also reduces load times and bandwidth requirements. If you can't use PHP then you could generate all the pages off-line and upload them as static HTML. Chris
