I’ve seen this behavior a number of times recently, it’s kind of ironic that the topic I clicked on which ended up prompting me to stop & start a topic is one about slow load times.
The issue at hand is that when I’m on a Topic A and client on a link at the bottom to Topic B, both the URL in my browser (chrome on mac) and the window’s title change quickly, but the topic title doesn’t change until after more of the page loads.
I’ve seen this here on meta more than anywhere else. Outside of making pages load faster, I wonder if the updating of the title itself should get prioritized?
Repro is visiting a topic, clicking on a suggested topic. The expectation is that the header would re-render right away with the new title / category and so on. Instead you see the spinner and old title.
The suggested topics list is done with raw handlebars, so each link is just a regular link that is run through our router. We know the URL to update right away because it comes from the link, but we don’t have the data object to use for the title / category.
(If it was a regular handlebars template we’d have an easy reference to the object for updating instantly like that.)
I think we have a component per row and it has the backing topic, it handles the click. Can it be extended to sort this out @eviltrout? (components/topic-list-item.js.es6)?
Isn’t it always the way that simple appearing things are always more complicated? There were a lot of edge cases due to the topic title not always being visible, and it depending on a “loaded” state.
It took a while, but I think I managed to make our application a lot smarter about showing topic titles when navigating to them from topic lists.
