Clicking "Save and Preview" when a preview is already open in a separate browser tab causes the preview to show the published version of the content item.

[stephen-sherman]

Which Umbraco version are you using?

16.3.4, 16.4.0, 17.0.0

Bug summary

Clicking "Save and Preview" when a preview is already open in a separate browser tab causes the preview to show the published version of the content item.

Reproduced in clean installations of Umbraco 16.4.0 and 17.0.0, and in two deployed instances of Umbraco 16.3.4.

Specifics

No response

Steps to reproduce

• Create a content item from a document type with template and enter some content
• Click Save and publish
• Make a content change
• Click Save and preview
  • A new browser tab opens. It shows the latest saved version of the content item, as expected
• Without closing the preview tab, return to the content editing tab
• Make a content change
• Click Save and preview
  • The browser swaps to the previously opened preview tab. It shows the latest published version of the page

Expected result / actual result

Expected result

Preview mode should always show the most up to date version of the content item

Actual result

Preview mode can enter a state where it shows the last published version of the content item, even though a more recently saved version is available

[github-actions]

Hi there @stephen-sherman!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[iOvergaard]

I can reproduce this, and I have prepared a fix intended for version 17.1.0.

[leekelleher]

Fixed in #20992, for Umbraco 17.1.0.