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

Make selfoss navigable #243

Closed
makkes opened this issue Apr 11, 2013 · 3 comments
Closed

Make selfoss navigable #243

makkes opened this issue Apr 11, 2013 · 3 comments

Comments

@makkes
Copy link
Contributor

makkes commented Apr 11, 2013

Currently when you're navigating around in the application the URL in the browser's address bar doesn't change (except for the "#sources" fragment which btw. doesn't work also).

It would be really helpful to have working URLs for different areas of the application. Examples:

Could be "https://domain/#newest" also but I'd prefer using the History API for this because fragments cause various problems and are ugly.

@GLLM
Copy link
Contributor

GLLM commented Apr 27, 2013

Good idea for tags + newest/unread marks :)

@virtadpt
Copy link

I like this idea, too!

niol added a commit to niol/selfoss that referenced this issue Dec 22, 2016
This pages modifies the client ui to make heavy use of location.hash: hash
changes are now responsible for loading the entry list.

Another big change is that the server side template is basically empty of any
data. It is loaded via the same client side code responsible for updating
item lists, tags, stats, etc.
@jtojnar jtojnar added the ui label Feb 5, 2017
jtojnar pushed a commit that referenced this issue Feb 5, 2017
This pages modifies the client ui to make heavy use of location.hash: hash
changes are now responsible for loading the entry list.

Another big change is that the server side template is basically empty of any
data. It is loaded via the same client side code responsible for updating
item lists, tags, stats, etc.
niol added a commit to niol/selfoss that referenced this issue Feb 6, 2017
This pages modifies the client ui to make heavy use of location.hash: hash
changes are now responsible for loading the entry list.

Another big change is that the server side template is basically empty of any
data. It is loaded via the same client side code responsible for updating
item lists, tags, stats, etc.
jtojnar pushed a commit that referenced this issue Feb 12, 2017
This pages modifies the client ui to make heavy use of location.hash: hash
changes are now responsible for loading the entry list.

Another big change is that the server side template is basically empty of any
data. It is loaded via the same client side code responsible for updating
item lists, tags, stats, etc.
@jtojnar
Copy link
Member

jtojnar commented Feb 12, 2017

Fixed in #869

@jtojnar jtojnar closed this as completed Feb 12, 2017
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

4 participants