Discourse ctrl+f search, even more useless than normal search
-
Seriously.
Web browsers have this Ctrl+F feature for the last 10 years. You type in word and you can search and jump instantly.
Ctrl+F withd iscourse and you get the search box and you get links.
No instant jump.Seriously?
I have to fucking click through links?
Jeff, IF I EVER SEE YOU AT ANY FUCKING CODE CONVENTION, EVENT OR ANYTHING, YOU ARE GETTING A SHOTGUN TO THE FACE.
-
Fun fact. Ctrl-F twice will fire up the browser finder, or Ctrl-F while in the editor.
Thing about the find business, you can't rely on Ctrl-F normally anyway because Discourse buggers about with the DOM to the point where points scrolled sufficiently far off screen get unloaded so Ctrl-F won't find them anyway...
-
It's all right though, because DiscoSearch works very well and will easily find the things you need and definitely won't return anything unrelated or miss anything
It's all right though, because DiscoSearch won't return anything
FTFM
-
Finding things is a barrier to civilized discussion.
It might be of interest to you that the Discourse-Team is "improving" the Search-Bar on top.
https://meta.discourse.org/t/double-stuf-improved-search-feedback/19490Filed Under Gotta love that screenshot Sam posted because as far as I can tell only 1 of the 5 Results actually features both search and narrow and that is the third one!
Filed Under: sigh Also it's clearly the browser searching wrong! The way Discourse handles content is flawless
-
Seriously.
Web browsers have this Ctrl+F feature for the last 10 years. You type in word and you can search and jump instantly.
Ctrl+F withd iscourse and you get the search box and you get links.
No instant jump.Seriously?
I have to fucking click through links?
Jeff, IF I EVER SEE YOU AT ANY FUCKING CODE CONVENTION, EVENT OR ANYTHING, YOU ARE GETTING A SHOTGUN TO THE FACE.
And that's why I like Firefox's 'Find as you type' feature :)Also, Discourse doesn't override F3. Not yet anyway...
Can websites override F-keys?
-
-
This old @cpradio post cracked me up:
https://meta.discourse.org/t/frustrated-with-search-in-discourse/13064/4?u=boomzilla
Money quote (from February 2014, so before we got our hands on Discourse):
Keep in mind, we are all fairly technical and have learned how to eventually get to the topic we want by altering our search criteria until it finds what we were looking for. But I issue the following challenge .... are we doing it wrong?
-
Yea, and I still agree 100% with what I said then, today. It still has the same issues, the excerpt definitely helps, but it really needs to be re-done.
-
Definitely. Search really needs to be their number one priority.
-
And my issues from back in June are still not addressed.
http://what.thedailywtf.com/t/discourse-search-requests/977?u=abarker
The strangest one is using the search terms "sacrific", "sacrifice" and "sacrificed" without constraining your search to the current topic.. Using "sacrific" or "sacrificed" will include I'm A Grumpy Cat: An open letter to Alex in the search results. Using "sacrifice" will not include that topic, even though it is the halfway point between the other two terms. How in Belgium do you even accomplish that?
Filed Under: I think they just made it prettier
-
And my issues from back in June are still not addressed.
Which I guess I rediscovered, with a different example, here.
Relevant excerpt from some posts above the linked one, to finish out your filed under:
I think they just made it prettier
@ChaosTheEternal said:instead of, you know, making the search work better
Wait, cross topic quotes no longer have an arrow to go to the post in the linked topic?
-
Filed Under: I think they just made it prettier
It's a little more than that. The context is a nice addition (though still no substitute for a full page interface).
-
Yes. <small>So keep your voice down</small>no! don't even think about that! if some marketdroid gets a wind of that then we'll all be in deep [excrement, extremely vulgar]!
the correct answer is: No, you cannot override keys.
-
Wait, cross topic quotes no longer have an arrow to go to the post in the linked topic?
Yup, another "removed feature", which makes the site less usable.
-
Was it too noisy for Jeff?
-
They really need to find a way to keep posts loaded in the DOM so browser search works. But given the charlie-fox of software platforms in use, getting halfway-decent performance with everything loaded is probably impossible.
-
But given the charlie-fox of software platforms in use, getting halfway-decent performance with everything loaded is probably impossible.
This is the key. Normal forums and websites don't have this kind of problem, because their plain text isn't surrounded by layers of unnecessary bullshit to deal with the same-code-different-results-client-server parsing of three different markup languages and an auto-loading-unloading delivery system.
-
Normal forums and websites don't have this kind of problem, because their plain text isn't surrounded by layers of unnecessary bullshit to deal with the same-code-different-results-client-server parsing of three different markup languages and an auto-loading-unloading delivery system
Eh...they also break shit up into pages. And the user doesn't expect the browser search to navigate to other pages in its search.
-
Eh...they also break shit up into pages. And the user doesn't expect the browser search to navigate to other pages in its search.
Quite, and they generally provide (or, and usually better, delegate to google) a "full thread / full forum" search feature.Discourse, on the other hand, pretends to load everything into one big page, and then fails to deliver the expected "if I search for 'text' on this page, I will have every instance of 'text' delivered to me". It clashes with the normal expectations of browser behaviour. Like almost everything else they've overridden.
-
They may as well create their own browser at this point.
-
Don't give them ideas.
-
They may as well create their own browser at this point.
For v1.01 they plan to duplicate the annoying "Would you like to install our native Tapatalk application?" bullshit that I get on other forums. No, I do not want your stupid fucking application and I do not want to be prompted every, single, time, I visit a forum you fucking shitbags. I just want to know the answer to an obscure question, which is mostly how I end up on forums.
Except for these forums. I come here to contribute to @blakeyrat's next eventual ragequit.
-
They should just licence fucking Clippy and be done with it
-
-
They should just licence fucking Clippy and be done with it
We shall dub him "Toastery".
"It looks like you are composing a reply. Please consider replying to more than one post at a time, do not use caps in excess, be helpful and informative...message truncated...by continuing to use Discourse you agree to relinquish your first born children to Atwood's Soylent Green..."
"Wait? WTF did that toaster just say?"
-
I'm sure this has been noticed before back during the early days of TDWTF on Discourse, but I'll mention it again to highlight the discoursistency.
We all know Ctrl+F opens Discosearch in a topic. But on the topics list page, Ctrl+F opens the browser search
-
recent change
-
So, it used to be consistent but they decided consistency was bad and removed it from the topics list page?
-
Yes. So keep your voice down
They can also override the arrow keys. Which is one of the most annoying things I've come across.
-
They really need to find a way to keep posts loaded in the DOM so browser search works. But given the charlie-fox of software platforms in use, getting halfway-decent performance with everything loaded is probably impossible.
The example of what happens in dicsourse when they keep a lot of things in EmberJS's memory is displayed in all its glory on your profile page's "All" listing. Scroll back a few dozen pages and watch your browser come to a screeching halt.
It would work fine, of course, if they just left the dom in the dom and didn't have a 10 ton javascript framework hulking around it.
-
So why did they make the search box longer anyway? Is it to entice you to type in a longer phrase and guarantee yourself 0 results?
Oh, it's so they can show a longer preview of the search results. It sure looks goofy when nothing has been searched yet and you get an input box long enough for a full freaking paragraph.
-
It would work fine, of course, if they just left the dom in the dom
and didn't have a 10 ton javascript framework hulking around it.I was just looking at the code and.... yeah, pretty sure that lag could be fixed if
#each(provided by the framework) was used instead of#groupedEach(custom).
-
So it's bad code, not bad design - my bad, I should at least assign the blame where it truly belongs if I'm going to be a dick about it.
-
-
Oh no we're not going there again
-
-
?
-
Your tea has gone mouldy.
-
We don't like muffins around here. We want no muffins, no toast, no teacakes, no buns, baps, baguettes or bagels, no croissants, no crumpets, no pancakes, no potato cakes and no hot-cross buns and definitely no smegging flapjacks.
And no, I'm not a waffle man either.
-
How about a cheese and ham brabble?
-
no
-
I have a 16-pound lump hammer you can borrow ;)
-
If in doubt, bigger hammer indeed
However I am in a fantastic mood this morning despite not sleeping well, so I shall spare the Talkie Toaster the invitation (but thank you)
-
.___________. | | ___________. | | /~\ | / __ __ /| | _ _ |_| | / /:/ /:/ / | !________|__! / /:/ /:/ / | | / /:/ /:/ / |____________! / /:/ /:/ / | ---------------- / /:/ /:/ / | _/ Would anyone \ / ~~ ~~ / | \ like any toast? / |~~~~~~~~~~| | ---------------- | :: | / | == | / | :: | / | :: | / | :: @ | / !__________!/Flagrantly stolen from here.
-
Bong and a blintz?
-
Not quite.
-
Scones.
Filed under: Dammit, now I want a scone, which is a thing not easily acquired while
reading TDWTFworking at work.
-
Oh man I just ate the SHIT out of a blueberry scone. It was delicious.
-
Oh man I just ate the SHIT out of a blueberry scone. It was delicious.
Sounds like someone is Baking It Wrong.
-
