Remember me

Lost Password?

Register now!


Who's Online
87 user(s) are online (72 user(s) are browsing Forums)

Members: 1
Guests: 86

NinjaCyborg, more...

Support us!


Report message:*

Re: NetSurf issues & wishes

Subject: Re: NetSurf issues & wishes
by ChrisH on 2016/9/9 18:40:32

@Chris Quote:
New blank tabs are always immediately switched to now too.

Thanks, this is a big usability improvement for me (although I was gradually getting used to working-around the issue).

OK, the "bring screen to front" when a new tab has opened due to a re-launch, is done. It only occurs if the new tab is active. I'm wondering whether it's more appropriate to always make this tab active.

I didn't understand the point you were making here, but what I found was the it still does NOT bring NetSurf to the front in the following cases:

If NetSurf is running, but I forgot it was, and run it again. It creates a new tab, but does not bring NetSurf's screen to the front. I'm not sure whether or not creating a new tab is a good idea, but in either case I think it should still bring NetSurf's screen to the front.

I previously said:
* "tab_new_session:1" does not bring the screen to the front, when the window is already open. This behaviour seems annoyingly inconsistent, since it does come to the front if NetSurf wasn't already running. I'm not sure whether the best solution is to (1) stop NetSurf bringing it's window/screen to the front when it is first created when opening a link (is that even possible... or desirable?), or (2) Simply always bring the window/screen to the front (when opening a link), despite "Open new tabs in background" (seems a bit strange & potentially unwanted).

FWIW, it's still the case that AppDir:NetSurf URL "http://my.url" creates a new tab without bringing the main screen to the front. (I did not yet test what happens if it is not running.) I don't know if you intended to change this behaviour or not, but thought I'd mention in anyway. As I said, I'm not sure what the 'right' solution is.

Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project