"Pinning" the Topic Summary window

UX
,
1

When the Topic Summary contains links to specific posts, it’s helpful to click on the links for more detail. On https://meta.discourse.org, when you click, the summary window remains open, which is great. But on my site and https://discuss.ai.google.dev, clicking on a link dismisses the summary window, which is cumbersome. What’s the secret to make it stay open?

1 Like
2

Can you explain what you mean by the topic summary window? I assumed you mean the modal that pops up when you click the summarise button, but on your site that is moving as expected.

image
image1245×940 133 KB

1 Like
3

We had a bug where it would close on click if the post was on another “page”, but I believe we fixed that. Did you try updating your site ?

1 Like
4

I’ll use your screenshot as an example.

On meta, if I click on Monalika’s comment, it would navigate to that comment, and the “Topic summary” modal would stay open, so I could then click on Shubham’s comment, then afirstenberg’s, etc., so I could easily browse the most important posts.

On my site, and at https://discuss.ai.google.dev/, if I click on Monalika’s comment, it would navigate to that comment, and the “Topic summary” modal would close.

If you can’t reproduce that, it may be related to a lot of errors in my console- 429 too many requests, related to rsvp.js and getting user badges. They happen when I click the links. Here are just the first few:

image
image757×567 38 KB

Yes, I did that today.

1 Like
5

Ah right – I thought you were referring to the Google site, not another one. What version are you running?

1 Like
6

Oh I see what this is, this happens on long topics.

If the “section” of the topic is not currently loaded then we shut the summary down on click.

Repro is:

  1. Have a topic with 30 posts
  2. Go to post 30 direct from home page
  3. Show summary
  4. Click on a link that goes to post #1
  5. Summary closes

Not 100% sure how to sort this out… maybe @keegan has some ideas.

3 Likes
7

Does that also explain the 429 errors getting the user badges, or is that a separate issue?

1 Like
8

That means you are using the cursed theme component “Post Badges”.

@david recently changed it to make it perform well, but you need to update Discourse to latest to get it.

1 Like
9

Yeah, this is a regression of the new design. We reported it internally back in August, but looks like no one was assigned. Will prioritize it.

4 Likes
10

This has now been resolved by @awesomerobot :tada:

Testing on this topic shows that it works

4 Likes