Page Search
-
I have a problem with this too. I really, really, hate taking away the default ctrl-f behaviour away from the user.
That said, have many other dragons to slay at the moment, but trust me it's a problem I want to figure out while trying to keep everybody happy
No matter what you search, it returns no posts
this should actually work though, can you file some repro steps if so?
-
Oy, it's not supposed to do that. It broke a version of two ago and I haven't had a chance took look into it.
Anyway, it's supposed to bring you to the search bar, but only in a topic otherwise the ctrl f is not jacked. From there a search will show a prev/next overlay and take you from post to post.
So no, it's not supposed to take you to the search page.
-
I think that's what he means. It's the inconvenience of being sent away to a search results page when you're looking for something potentially right in your face (let's say, post with 10 paragraphs, and you know the default ctrl-f will help you find what you're looking for)
EDIT: but yeah, it actually is broken atm, the in-topic search does not work for me. Also the cursor should really be sent to the end of the input box, right now I get
in:topic-2769but my cursor is at the start of that. I would also say that the "programmer jargon" in that search is less than intuitive for most normal folk. -
People are alienated when they don't come across their expected UX behaviour tbh. Not sure what the right solution is here atm
-
I can see the use of it when using infinite load to search in topics that aren't loaded yet. Rather than entering the whole
in:topic-2769, could that not be a hidden field? So you can just type what you're looking for. When it works, that would be more intuitive, but it's very hit and miss, sometimes it loads browser default, sometimes it doesn't. (You have to click somewhere in the topic first for the find in topic to open).I'll have a think about it while I watch Prison Break (again)
-
One thing that really bothers me that I've seen on other implementations is:
Let's say I came from google searching for "keyword anotherkeyword", and I stumble upon post 1000 out of 1500 about a topic regarding "keyword".
This post has 10 paragraphs, and I really just want to find that sentence I googled, so let me hit ctrl-f and type "keyword"
Bam I'm on page 1. Since this topic is about "keyword" now have to sift through potentially 999 other results before I get to that post which I initially landed on from the search engine.
It's a real UX problem, something that I refuse to just bandaid and forget about it, so yeah. I'm declaring war
-
One problem I have encountered is that if Search has been disabled for Guest users, the ability to CTRL+F on a topic page is effectively completely gone, because the user does not have the required privileges to use the search functionality that is overriding the browser's default CTRL+F behaviour.
That said, it is my opinion that CTRL+F should produce consistent behaviour throughout the entire site. Completely changing the way it works on topic pages only is highly counter-intuitive.
@a_5mith said:
I can see the use of it when using infinite load to search in topics that aren't loaded yet.
In that case, would it not be better to simply load any not-yet-loaded posts upon the pressing of CTRL+F instead of replacing it entirely on certain pages?
-
@Xiph said:
would it not be better to simply load any not-yet-loaded posts upon the pressing of CTRL+F
Unfortunately that wouldn't scale. If you pressed ctrl-F on page one of a 200 page topic, you'll explode your browser
Completely changing the way it works on topic pages only is highly counter-intuitive.
See, I always alienate somebody XD I figured having the ctrl-F-jacking only on the topic page would be less invasive, but somehow it's more.
Browser search function being something we can't alter, we're left with removing the in-topic search system altogether (not that it's even working right now), so we're back to square one.
-
@julian said:
@Xiph said:
would it not be better to simply load any not-yet-loaded posts upon the pressing of CTRL+F
Unfortunately that wouldn't scale. If you pressed ctrl-F on page one of a 200 page topic, you'll explode your browser
Just wondering, how then would the current in-topic system avoid that problem when it's not erroneously redirecting you to the search page?
@julian said:
See, I always alienate somebody XD I figured having the ctrl-F-jacking only on the topic page would be less invasive, but somehow it's more.
The problem for me is the inconsistency: if every other page also exhibits the same or extremely similar behaviour (in this case, jumping to the search field up top), I wouldn't have a problem with it.
(Of course it's usually better not to override default browser functionality... hint hint
)
