Chrome back button (newly) steals page focus
Last night I updated to Chrome 70.0.3538.77 (Official Build) (64-bit) on my Mac (Sierra). I'm now seeing the following new behavior: after using the "back" button, the page I've gone back to doesn't have focus. That is, if I use the arrow or page up/down or home/end keys to navigate the page, nothing happens. I have to click in the page to get the focus again.
This doesn't happen when I navigate to a page via links; after the page load, these keys work as expected. It's only when going back, and only with this update. (I had 68.something before; apparently I skipped 69.)
I disabled user scripts and tried several sites -- Stack Exchange sites, XKCD, weather.com all behave this way. I found something in searching that suggested it might have to do with iframes, so I tried on a bare-bones HTML page (hand-written) with nothing fancy going on, and it happens there too.
While waiting for Google to fix this, is there something I can do to force the page to have the correct focus? If there targets within the page (such as a search box), ideally the focus would be wherever it would have been were that page freshly loaded instead of reached via "back".
google-chrome
add a comment |
Last night I updated to Chrome 70.0.3538.77 (Official Build) (64-bit) on my Mac (Sierra). I'm now seeing the following new behavior: after using the "back" button, the page I've gone back to doesn't have focus. That is, if I use the arrow or page up/down or home/end keys to navigate the page, nothing happens. I have to click in the page to get the focus again.
This doesn't happen when I navigate to a page via links; after the page load, these keys work as expected. It's only when going back, and only with this update. (I had 68.something before; apparently I skipped 69.)
I disabled user scripts and tried several sites -- Stack Exchange sites, XKCD, weather.com all behave this way. I found something in searching that suggested it might have to do with iframes, so I tried on a bare-bones HTML page (hand-written) with nothing fancy going on, and it happens there too.
While waiting for Google to fix this, is there something I can do to force the page to have the correct focus? If there targets within the page (such as a search box), ideally the focus would be wherever it would have been were that page freshly loaded instead of reached via "back".
google-chrome
add a comment |
Last night I updated to Chrome 70.0.3538.77 (Official Build) (64-bit) on my Mac (Sierra). I'm now seeing the following new behavior: after using the "back" button, the page I've gone back to doesn't have focus. That is, if I use the arrow or page up/down or home/end keys to navigate the page, nothing happens. I have to click in the page to get the focus again.
This doesn't happen when I navigate to a page via links; after the page load, these keys work as expected. It's only when going back, and only with this update. (I had 68.something before; apparently I skipped 69.)
I disabled user scripts and tried several sites -- Stack Exchange sites, XKCD, weather.com all behave this way. I found something in searching that suggested it might have to do with iframes, so I tried on a bare-bones HTML page (hand-written) with nothing fancy going on, and it happens there too.
While waiting for Google to fix this, is there something I can do to force the page to have the correct focus? If there targets within the page (such as a search box), ideally the focus would be wherever it would have been were that page freshly loaded instead of reached via "back".
google-chrome
Last night I updated to Chrome 70.0.3538.77 (Official Build) (64-bit) on my Mac (Sierra). I'm now seeing the following new behavior: after using the "back" button, the page I've gone back to doesn't have focus. That is, if I use the arrow or page up/down or home/end keys to navigate the page, nothing happens. I have to click in the page to get the focus again.
This doesn't happen when I navigate to a page via links; after the page load, these keys work as expected. It's only when going back, and only with this update. (I had 68.something before; apparently I skipped 69.)
I disabled user scripts and tried several sites -- Stack Exchange sites, XKCD, weather.com all behave this way. I found something in searching that suggested it might have to do with iframes, so I tried on a bare-bones HTML page (hand-written) with nothing fancy going on, and it happens there too.
While waiting for Google to fix this, is there something I can do to force the page to have the correct focus? If there targets within the page (such as a search box), ideally the focus would be wherever it would have been were that page freshly loaded instead of reached via "back".
google-chrome
google-chrome
asked Nov 1 '18 at 13:40
Monica CellioMonica Cellio
177117
177117
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This has been driving me nuts as well. It doesn't happen when I use Command-Left Arrow to navigate back, instead of clicking on the back button. I also installed the Go Back With Backspace extension, which lets me use the backspace key as a shortcut. (Another feature Chrome broke a while back.)
Thanks! I never thought to try a keyboard shortcut. I'll attempt to train myself to do that.
– Monica Cellio
Jan 30 at 3:45
I think I used to use the keyboard, but untrained myself when they removed the backspace shortcut. Now I'm attempting to retrain myself to use the keyboard again.
– Jim Ancona
Jan 30 at 18:43
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1371876%2fchrome-back-button-newly-steals-page-focus%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This has been driving me nuts as well. It doesn't happen when I use Command-Left Arrow to navigate back, instead of clicking on the back button. I also installed the Go Back With Backspace extension, which lets me use the backspace key as a shortcut. (Another feature Chrome broke a while back.)
Thanks! I never thought to try a keyboard shortcut. I'll attempt to train myself to do that.
– Monica Cellio
Jan 30 at 3:45
I think I used to use the keyboard, but untrained myself when they removed the backspace shortcut. Now I'm attempting to retrain myself to use the keyboard again.
– Jim Ancona
Jan 30 at 18:43
add a comment |
This has been driving me nuts as well. It doesn't happen when I use Command-Left Arrow to navigate back, instead of clicking on the back button. I also installed the Go Back With Backspace extension, which lets me use the backspace key as a shortcut. (Another feature Chrome broke a while back.)
Thanks! I never thought to try a keyboard shortcut. I'll attempt to train myself to do that.
– Monica Cellio
Jan 30 at 3:45
I think I used to use the keyboard, but untrained myself when they removed the backspace shortcut. Now I'm attempting to retrain myself to use the keyboard again.
– Jim Ancona
Jan 30 at 18:43
add a comment |
This has been driving me nuts as well. It doesn't happen when I use Command-Left Arrow to navigate back, instead of clicking on the back button. I also installed the Go Back With Backspace extension, which lets me use the backspace key as a shortcut. (Another feature Chrome broke a while back.)
This has been driving me nuts as well. It doesn't happen when I use Command-Left Arrow to navigate back, instead of clicking on the back button. I also installed the Go Back With Backspace extension, which lets me use the backspace key as a shortcut. (Another feature Chrome broke a while back.)
answered Jan 30 at 3:41
Jim AnconaJim Ancona
261
261
Thanks! I never thought to try a keyboard shortcut. I'll attempt to train myself to do that.
– Monica Cellio
Jan 30 at 3:45
I think I used to use the keyboard, but untrained myself when they removed the backspace shortcut. Now I'm attempting to retrain myself to use the keyboard again.
– Jim Ancona
Jan 30 at 18:43
add a comment |
Thanks! I never thought to try a keyboard shortcut. I'll attempt to train myself to do that.
– Monica Cellio
Jan 30 at 3:45
I think I used to use the keyboard, but untrained myself when they removed the backspace shortcut. Now I'm attempting to retrain myself to use the keyboard again.
– Jim Ancona
Jan 30 at 18:43
Thanks! I never thought to try a keyboard shortcut. I'll attempt to train myself to do that.
– Monica Cellio
Jan 30 at 3:45
Thanks! I never thought to try a keyboard shortcut. I'll attempt to train myself to do that.
– Monica Cellio
Jan 30 at 3:45
I think I used to use the keyboard, but untrained myself when they removed the backspace shortcut. Now I'm attempting to retrain myself to use the keyboard again.
– Jim Ancona
Jan 30 at 18:43
I think I used to use the keyboard, but untrained myself when they removed the backspace shortcut. Now I'm attempting to retrain myself to use the keyboard again.
– Jim Ancona
Jan 30 at 18:43
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1371876%2fchrome-back-button-newly-steals-page-focus%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown