When I include a link to a section in a page - that link, when clicked, does not modify the browser history. Navigating back proceeds to navigate away from the pager, rather than return to page position where the link is defined. Edit: Well on this Discourse I’m unable to create an element with an …

This is kinda of expected. If you click a link to another post in the same topic it is also not pushed into the history stack, and it is a full link without fragments, so we never push in-topic into the history.

I find this behavior extremely unexpected :slight_smile: Here’s a sample page with no JavaScript. On Chromium, clicking that link takes you to the bottom of the page. Clicking back takes you back to where you clicked from. That’s expected behavior that you’ll see on every other website that doesn’t…

Here’s an example of where this behavior is problematic: https://meta.discourse.org/tos If you’re tempted to click any of the TOC links and then return to your starting point via browser history, you can’t. Why provide a TOC in the first place? For those sites that would like to support the stan…

Depending on the context which you’ll use your anchors in, maybe this table of content plugin could be useful (and in my opinion that would fit well on the TOS and FAQ page)? Example here .

I never realized this was bothering me until you pointed it out. I’ve often tried to go back to where I clicked a link in Discourse and instead ended up on a previous page. Very irritating. I always chalked it up to a combination of the iOS app, since I use it for almost all Discourse stuff, and use…

This TOC component is really well done and we’re using it in every docs page - very grateful for the work put into it! The issue of navigation remains however. Clicking a link in the TOC does not modify the browser history and therefore navigating back navigates off the page.

[imagen] gar1t: The issue of navigation remains however. Clicking a link in the TOC does not modify the browser history and therefore navigating back navigates off the page. This is certainly the case, It would be nice to fix this @Johani but I have a feeling it is very complicated. Maybe we …

I implemented a work-around (arguably a proper approach to customize a site given Discourse’s point-of-view on link navigation) via a theme component. This follows the pattern used by DiscoTOC where a marker is added to a post to trigger the behavior. The applicable code is here . I think modifying …

careful with pushstate there… what you probably want is replacestate.

I think pushState in this case. The goal is to enable back-to-previous-position, which requires a push to history because the event is prevented.

Navegar a un fragmento de URL local no modifica el historial del navegador

Soporte

sam (Sam Saffron) 24 Junio, 2020 00:24 10

ten cuidado con pushstate allí… lo que probablemente necesitas es replacestate.

Dropping ad revenue

Tema		Respuestas	Vistas
Push browser history when navigating within a topic Feature	7	1132	25 Febrero 2019
Clicking an internal link with slug only and no topic ID should create a history entry Bug	8	1421	22 Julio 2021
Discourse Disable Browser History Experiment Plugin experimental	0	4771	11 Junio 2014
External links in history don’t follow “Open all external links in a new tab” setting Bug	36	6446	3 Mayo 2016
TOC missing after using browsers back button Bug disco-toc	8	556	25 Enero 2024

Navegar a un fragmento de URL local no modifica el historial del navegador

Temas relacionados