Should linking to other topics cause the browser window to refresh?

AI 生成的摘要

The discussion revolves around whether clicking internal links on Discourse should refresh the browser window. jamesmarkcook initially experienced a full window refresh when clicking internal links with full paths, but discovered that relative paths load content dynamically without a refresh. They wondered if it’s possible to have a nicely formatted preview while still loading content dynamically. codinghorror requested a demonstration, which jamesmarkcook provided, highlighting the difference between full path and relative path links. The issue was later addressed by eviltrout, who fixed the problem related to https usage with a commit on GitHub.

Title says it all.

I was expecting clicking an internal link to load in the same way as everything else, but my browser is refreshed as if visiting an external link.

UPDATE

It’s because I used the full path (http://meta.discourse.com/t/sometopic) rather than the relative path. However, this is how the majority of non-technical people will use links on Discourse, so my question remains.

As a side note, the full path uses one box giving a nicely formatted preview, whereas the relative path provides just the link text. What am I doing wrong?

2 个赞

I have no idea what you are talking about here? Can you post a link in a reply to demonstrate?

By clicking the first link, it refreshes the entire window, instead of just loading the topic using Ember.

https://meta.discourse.org/t/creating-wp-native-comments/47557/13

Using the second link, it loads the topic dynamically instead of refreshing the entire page. Is there a reason why we can’t have a preview of a topic and load it like the second link?

4 个赞

It is a subtle distinction, but let’s ask @eviltrout.

1 个赞

Nice catch. It was a https uses that I’ve fixed here:

https://github.com/discourse/discourse/commit/b6bcfc0426f123e159935b079969216b76e1eccc

7 个赞