New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improvements for :navigate prev/next heuristics #6696
Comments
I had a look at the duckduckgo page and it looks like there are two problems. The first is that the correct element is called "More results" while the page also contains a bunch of other elements with the word "more", e.g. "more images" and the element that leads to the information page about bangs. The second problem is that even when
more results aren't loaded and the tab title is changed to |
Maybe this is unrelated, but shouldn't Another option would be to follow Vimium's approach and let the user define a set of symbols for calling |
@agenbite there are the |
That's great! Thank you so much for this so well-thought software!! However, I'm not being able to make it work in this case. Apparently it has nothing to do with language, after all. The code involved in navigation is this:
I've tried this:
To no avail so far. :( Any help would be appreciated. |
I think there are two things stopping us from picking up the buttons on that site:
|
Would this be the same thing that happens with Twitter's next/prev image? I get:
When browsing the images of this tweet. If that's the case, maybe it'd be nice to have the 'aria-label' and/or button considered... |
As reported by keir in IRC, using
]]
on ddg result pages results in loading some kind of "more information" link for bangs being loaded, rather than the "more results" button.The text was updated successfully, but these errors were encountered: