The discussion addresses a feature request to improve navigation for quoted posts. Dotila_Li suggested that clicking the quote button should jump directly to and highlight the specific quoted text, rather than requiring users to scroll through long posts.
zogstrip confirmed the implementation via a pull request. While singpolyma praised the new slide-out functionality, they reported a bug where the “go to quoted post” button failed to navigate correctly, only reloading the page. After reproducing the issue, zogstrip committed to fixing it.
A secondary interaction occurred between seanblue and zogstrip regarding whether the feature expands collapsed sections. Seanblue asked if the code would handle this, but zogstrip repeatedly directed them to test it on try.discourse.org instead of answering directly. This led to a brief dispute over communication styles, with seanblue noting that testing requires setting up a new account, while zogstrip maintained that direct answers were unnecessary when the environment was available.
It could be useful if we click this button, then jump to the quote in the quoted post diractly, and highlight the quote.
I know the left drop down button can show the highligted quote too, but it doesn’t jump diractly to the quote, we have to scroll to the highligted. When the quoted post is long, it’s a bit annoying to scroll.
@Dotila_Li / @singpolyma i’ve got some good news 
Nice! The slide-out works perfectly, exactly how I’d want. Though I find that the “go to the quoted post” button now seems to do nothing, just reload the page and keep scroll position…
do you have a way i can reproduce this?
if you need a test env, feel free to use https://try.discourse.org
I managed to reproduce here A quoting test for testing jump to quote - #3 by singpolyma - general - Discourse Demo if I click the “go to quoted post” on id in sapien it seems to just reload and stay in the same place.
thanks 
will investigate and fix.
Will this also expand collapsed sections if the quote happens to be within one?
why don’t you try it instead of asking
Because in the past I’ve been told not to make posts solely to test features.
here on meta, sure - but go wild on https://try.discourse.org
Is there a particular reason you can’t just answer the question directly? It would have taken you less time than answering the way you did twice.
and it would have taken you less time as well to test that yourself
That’s absolutely not true since I’d have to set up a new account on https://try.discourse.org/, but whatever. I guess I’ll find out for myself in a couple months when the change makes its way to a site I already use.
