Skip to content
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

Search URI is not pushed to the address bar #399

Closed
karlcow opened this issue Nov 14, 2014 · 8 comments
Closed

Search URI is not pushed to the address bar #399

karlcow opened this issue Nov 14, 2014 · 8 comments

Comments

@karlcow
Copy link
Member

karlcow commented Nov 14, 2014

Step to reproduce:

  1. Go to http://webcompat.com/
  2. Log in
  3. Click see More
  4. Type a search term. for example: "is:issue is:open google in:title"

Expected:

to have the URI in the address bar to be something along (Not necessary this parameter syntax, just an example)
https://webcompat.com/issues/search?is=issue&is=open&q=google&in=title

Current:

The address is https://webcompat.com/issues

Why it's important.

It's currently not possible for someone to share a specific search URI on the Web or by mail.

Possible issues

When someone is not logged in to webcompat.com, the search URI will not be working. We could handled that case through a redirect to github search.

@miketaylr
Copy link
Member

👍

@miketaylr
Copy link
Member

When someone is not logged in to webcompat.com, the search URI will not be working.

I wonder if we could send a flash message like: "(Log in) to see search results. Or see the (search on GitHub)". Stuff in parens would be hyperlinks.

@karlcow
Copy link
Member Author

karlcow commented Nov 24, 2014

In the case of non-authentificated user we should send:

@miketaylr
Copy link
Member

Sounds like a good plan.

@miketaylr
Copy link
Member

Also need to include params like page, per_page, update closed=1, etc.

@miketaylr
Copy link
Member

Making progress on this. Pushing params to the URL is all done--and toggling filter params as well. I just need to hook up reading from the URL in loadIssues.

And then we need to tackle #516 (actually having and reacting to a state for the pushState). I don't think it will make much sense to deploy one without the other. Or at least it would feel very broken.

@hallvors
Copy link
Contributor

heh, Karl was already on it :)

@miketaylr
Copy link
Member

OK, I think I've got this one done. But I need to write some tests before sending a PR--there's a billion things to keep track of, which means I'll surely break it in the future. ^_^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants