On 30 Apr 2009, Richard Porter wrote: > On 30 Apr 2009 Roger Darlington wrote: > >> On 29 Apr 2009, Richard Porter wrote: >>> Netsurf's behaviour is a little bit inconsistent or at least >>> inconvenient with framesets. For example go to >>> http://www.bestmoments.at/catago/BestMoments/FE/Index/index >>> >>> and click on "ZU DEN BILDERN". The main frame changes but the back >>> icon is not enabled. However the menu allows you to select Navigate > >>> Back one page. Having gone back to the first page the reverse applies >>> and you can go forward one page using the menu but not the toolbar >>> icon. >>> >>> You need to click Menu in the main frame, so I can see what's >>> happening but it's not particularly helpful. It would be better if the >>> forward and back icons let you step through the 'pages' actually seen >>> regardless of their structure. I think most browsers do this. > >> By experimentation with one of my framed sites (no comments on my >> implementation of these sites please!) the way Netsurf has implemented >> forward/back via menu allows you to click 'menu' over the frame-pane >> that you wish to go backwards/forwards on. So, you could click on any >> frame-pane. > > Yes but unless you click on the frame that was last updated you won't > get the desired result. > >> Unfortunately, it doesn't update the menu pane when you >> click using 'right-click' - you have to click menu again to enable >> further navigation of the same frame-pane. > > Do you mean clicking on the right arrow?
No, right mouse click on Navigate>BackOnePage so that the menu stays up on screen. The BackOnePage item disappears (is greyed out) even if you have two BackOnePages to go to. > It only works if you go back > from the frameset to an earlier page, from where you can only return > to the initial state of the frameset. > >> However, Netsurf developers could implement this way of working and >> still use the navigate buttons, which is what they are there for after >> all: Click on the frame-pane you wish to navigate, then click on the >> appropriate Navigate button. > > That would be a possibility. Following a link in a frameset can only > update one frame, so it should be fairly easy to track in the history. > The browser needs to record the target frame, but it must already hold > the information for each frame so that shouldn't be too difficult. > > The tricky bit is when you leave the frameset for another page and > then try to go back to it in the same state that you left it in. You'd > need to go back and find what object was last loaded into each frame > (and framesets can be nested). And in my web-pages, the frames are nested. Oh well. Good job there's a brain behind the mouse which can also remember... > -- Cheers Roger "I suspect everyone, and yet, I suspect no-one" Inspector Cleuseau
