Pony: Don't send focus to search box when search results page loads August 15, 2013 6:59 PM Subscribe
When a search results page loads, the focus moves into the search box (in the form with id "sform"), and I wish it wouldn't.
I find this focus-moving behaviour inconvenient when I'm systematically or semi-systematically looking through search results: I click on one result to look at that particular thread more closely, then hit my browser's back button to return to the search results, wanting to continue looking through the results exactly where I left off, and my browser conveniently redisplays the page at the same vertical position as when I left it — but then the focus is moved back to the search box, my browser scrolls to show me what's in focus, and I have to find my place again. So, I'd like it if the focus were left alone.
(Also, of course, I'd like to hear if others find this behaviour convenient for some reason I've overlooked.)
I find this focus-moving behaviour inconvenient when I'm systematically or semi-systematically looking through search results: I click on one result to look at that particular thread more closely, then hit my browser's back button to return to the search results, wanting to continue looking through the results exactly where I left off, and my browser conveniently redisplays the page at the same vertical position as when I left it — but then the focus is moved back to the search box, my browser scrolls to show me what's in focus, and I have to find my place again. So, I'd like it if the focus were left alone.
(Also, of course, I'd like to hear if others find this behaviour convenient for some reason I've overlooked.)
Also, while we're at it, is it possible to turn off auto-correct in the search box on the iOS version of the site?
posted by Devils Rancher at 8:39 AM on August 16, 2013
posted by Devils Rancher at 8:39 AM on August 16, 2013
then hit my browser's back button to return to the search results, wanting to continue looking through the results exactly where I left off
open the link in a new tab, leaving the search result page. when finished, close the tab.
posted by quonsar II: smock fishpants and the temple of foon at 9:22 AM on August 16, 2013
open the link in a new tab, leaving the search result page. when finished, close the tab.
posted by quonsar II: smock fishpants and the temple of foon at 9:22 AM on August 16, 2013
I endorse this pony. Er....
posted by wenestvedt at 10:03 AM on August 16, 2013
posted by wenestvedt at 10:03 AM on August 16, 2013
...is it possible to turn off auto-correct in the search box on the iOS version of the site?
I think so, but that would disable it for everyone. It's not obvious to me why you'd want to disable it.
posted by pb (staff) at 12:19 PM on August 16, 2013
I think so, but that would disable it for everyone. It's not obvious to me why you'd want to disable it.
posted by pb (staff) at 12:19 PM on August 16, 2013
Search queries on MetaFilter are frequently not in the iOS dictionary. For example, when I try to search by username, some of which are... "unique," you might say, it tries to auto-correct it to a regular english word, and when I try to tap that little bitty x by the iOS autocorrect suggestion, half the time I miss & hit my username which it partially obscures, & get taken to my profile.
posted by Devils Rancher at 1:28 PM on August 16, 2013
posted by Devils Rancher at 1:28 PM on August 16, 2013
Yeah, I can sympathize, but I think that's more of a phone issue than a MetaFilter issue. People also look for words in the dictionary and it can handy to have autocorrect available.
...half the time I miss & hit my username which it partially obscures...
Where are you searching from on your phone?
posted by pb (staff) at 1:35 PM on August 16, 2013
...half the time I miss & hit my username which it partially obscures...
Where are you searching from on your phone?
posted by pb (staff) at 1:35 PM on August 16, 2013
Oh, I see, you're looking at the Standard View on your phone and using the search form at the top of the page. You might try navigating directly to the Search Page first. Then you won't have the username issue.
posted by pb (staff) at 1:37 PM on August 16, 2013
posted by pb (staff) at 1:37 PM on August 16, 2013
Oh, duh, my apologies, and good point.
I'm really talking about viewing on my iPad, which runs the regular version of the site, not the iOS version. The problem is that iOS on the iPad makes those annoying pop-up autocorrect suggestions just like the iPhone, and they're hard to hit the x on.
If the site by-and-large benefits from having auto-correct turned on in the search field, that's the way it rolls, I guess.
posted by Devils Rancher at 1:48 PM on August 16, 2013
I'm really talking about viewing on my iPad, which runs the regular version of the site, not the iOS version. The problem is that iOS on the iPad makes those annoying pop-up autocorrect suggestions just like the iPhone, and they're hard to hit the x on.
If the site by-and-large benefits from having auto-correct turned on in the search field, that's the way it rolls, I guess.
posted by Devils Rancher at 1:48 PM on August 16, 2013
ah ok. I guess the nuclear option for you is to disable spell-checking on your iPad. It's in General settings under Keyboard.
Otherwise, next time you're searching for something just click the button as if you typed something in. That'll take you to the results page (with no results) and you can start typing there.
posted by pb (staff) at 1:56 PM on August 16, 2013
Otherwise, next time you're searching for something just click the button as if you typed something in. That'll take you to the results page (with no results) and you can start typing there.
posted by pb (staff) at 1:56 PM on August 16, 2013
I think so, but that would disable it for everyone.
The input autocorrect and autocapitalize attributes are pretty much only recognized by iPhone and iPad. They're ignored by desktop browsers and Android phones and tablets which mainly focus on input suggestions rather than automatic corrections. That is, most people already have auto-correct disabled by virtue of not using an iOS device.
Disabling auto correct for iPad and iPhone wouldn't disable it for everyone, it would only disable it for people using iPhone and iPad. And if you limited the change to the member's search box then it would have an effect on even fewer people. You're swapping out a different version there anyway.
In any event, disabling at least auto-capitalization during a search for members seems like a reasonable request given the baroque capitalization of usernames. Even for non-username searches, a regular query doesn't seem like it should be capitalized.
posted by Jeff Howard at 6:53 PM on August 16, 2013
The input autocorrect and autocapitalize attributes are pretty much only recognized by iPhone and iPad. They're ignored by desktop browsers and Android phones and tablets which mainly focus on input suggestions rather than automatic corrections. That is, most people already have auto-correct disabled by virtue of not using an iOS device.
Disabling auto correct for iPad and iPhone wouldn't disable it for everyone, it would only disable it for people using iPhone and iPad. And if you limited the change to the member's search box then it would have an effect on even fewer people. You're swapping out a different version there anyway.
In any event, disabling at least auto-capitalization during a search for members seems like a reasonable request given the baroque capitalization of usernames. Even for non-username searches, a regular query doesn't seem like it should be capitalized.
posted by Jeff Howard at 6:53 PM on August 16, 2013
Yeah, I guess we could disable capitalization. The search itself is case-insensitive. So a search for 'Test' returns exactly the same results as 'test'. I don't think users are having to do extra work right now to get the capitalization just right in search input boxes.
I'm always hesitant to override default features of browsers. We do it in a few places and people are always annoyed by it. (Even though the browsers make annoying choices too.) So unless there's a strong reason to disable capitalization my first reaction is to leave it as is.
posted by pb (staff) at 7:53 PM on August 16, 2013
I'm always hesitant to override default features of browsers. We do it in a few places and people are always annoyed by it. (Even though the browsers make annoying choices too.) So unless there's a strong reason to disable capitalization my first reaction is to leave it as is.
posted by pb (staff) at 7:53 PM on August 16, 2013
AH, this search box focus is my #1 annoyance on Metafilter. Mainly because I use the space bar to page down, and on the search page, this just adds spaces before the search term. So I have to actually lift my hands from the keyboard to the touchpad to change focus (a tragedy, I know!). I think this is the first pony I've ever really wanted.
posted by bluefly at 6:39 AM on August 17, 2013
posted by bluefly at 6:39 AM on August 17, 2013
I also use the space bar to scroll and find the focus change really annoying. I would love it if this changed.
posted by Margalo Epps at 9:53 AM on August 17, 2013
posted by Margalo Epps at 9:53 AM on August 17, 2013
So I have to actually lift my hands from the keyboard to the touchpad to change focus (a tragedy, I know!).
An alternative is to tab twice to move the focus somewhere innocuous, and then space-to-scroll. (Tabbing just once puts the focus on the form submission button, and then space will re-do the search.) It's still a cognitive bump, but at least you're still on the keyboard.
posted by stebulus at 3:17 PM on August 17, 2013
An alternative is to tab twice to move the focus somewhere innocuous, and then space-to-scroll. (Tabbing just once puts the focus on the form submission button, and then space will re-do the search.) It's still a cognitive bump, but at least you're still on the keyboard.
posted by stebulus at 3:17 PM on August 17, 2013
We made this change today. If the page has a search term it won't send focus to the form.
posted by pb (staff) at 10:24 AM on August 19, 2013 [2 favorites]
posted by pb (staff) at 10:24 AM on August 19, 2013 [2 favorites]
You are not logged in, either login or create an account to post comments
I think focusing on the search box on a new search page is a good idea and saves time, but I can see this being a little annoying on search result pages. We'll think about it and see if others hit this snag often.
posted by mathowie (staff) at 7:40 PM on August 15, 2013 [2 favorites]