GNOME Bugzilla – Bug 151943
"focus stealing prevention" for page loads
Last modified: 2012-03-02 16:40:07 UTC
We've been working on timestamp-based "focus stealing prevention" in metacity, so if you launch a new window, then start doing something else, the new window will not get focus. Sometimes I start a page load, start doing something else, and then the newly-loaded page grabs focus. A common case is when opening a new browser window, the home page starts to load; my home page has an entry box on it, so grabs focus from the URI I'm typing. So the suggestion is that when starting a page load, record the X timestamp. If _NET_WM_USER_TIME is updated before the page finishes loading, don't move the focus to the page. Not sure if GDK exports good API for keeping track of this.
Mass reassigning of Epiphany bugs to epiphany-maint@b.g.o
> We've been working on timestamp-based "focus stealing prevention" in metacity > so if you launch a new window, then start doing something else, the new > window will not get focus. How does timestamping prevent stealing focus? Surely the focus will still be stolen, just a bit later?
compare the timestamp when the page load was initiated with the timestamp of the last user action; if the user has started doing something since the page load initiated, don't grab focus from what they are doing.
Is this bug talking about the same thing as bug 150085 ?
No, 150085 is focus of the epiphany window vs. other windows, this bug is about focus *within* the browser itself. There are various times the browser will jump focus somewhere within the web page when you're trying to type elsewhere.
I'd just like to confirm this bug. Epiphany's focus seems to jump around quite a bit. Initially it just seems like an annoying bug but I think it can be seen as something of a security risk. e.g. You are halfway through entering a password for a site, when the focus is taken the 2nd half of your password is visible because you have continued to type but the focus has been given elsewhere.
Isn't this a dupe of bug 105153 ?
Right. Galeon has some work-around for the focus bugs; I'm contemplating copying them. *** This bug has been marked as a duplicate of 105153 ***
Is this really a duplicate of 105153??? 105153 seems to be about the location bar not getting focus when you create a new tab. This bug is about focus jumping around when the user doesn't wish it.
I don't think it's a dup personally. Maybe I haven't made it clear enough what this bug is about?
*** Bug 312862 has been marked as a duplicate of this bug. ***
Havoc, can you try again with ephy 1.7.4?
While the most serious focus bug is fixed in 1.7.5 (1.7.4 has an unfortunate configure bug that prevents it from being enabled, ahem), this still looks like a good idea to solve the problem of where to put the focus when loading a new page in the active tab.
Was there progress on this? It appears to not have been resolved as of Epiphany 2.29.91 (Bug 611526).
*** Bug 611526 has been marked as a duplicate of this bug. ***
Apart from occasional crashes (might be from plugins), this is and was the most annoying bug in Epiphany. :) I think it was fixed when Epiphany was using the Gecko backend. I didn't see it for some years. But now with the Webkit backend, it's back. I saw it two minutes ago, on 2.30.2. I remember when I used the new Webkit backend for the first time, experiencing the bug again: this is Epiphany! It actually got me a bit excited, still the same good ol' browser in spite of the change underneath.
(In reply to comment #16) > Apart from occasional crashes (might be from plugins) Yes epiphany 2.30 crashes with the flash plugin, and it's not a flash plugin bug because the same plugin works with other browsers. > But now with the Webkit backend, it's back. I saw it two minutes ago, on > 2.30.2. > > I remember when I used the new Webkit backend for the first time, experiencing > the bug again: this is Epiphany! It actually got me a bit excited, still the > same good ol' browser in spite of the change underneath. I used epiphany/webkit for a long while and never had such a bug. Now I'm experiencing this bug with epiphany 2.91/gtk3.
This should work fine in master with recent webkitgtk. Please reopen if you still see this in epiphany master + webkitgtk 1.7.9x