QuickLaunch navigation (for SinglePageWebParts) fails

[ng-marcus]

Category

• Bug

Describe the bug

On some tenancies, we are seeing clicks on the left hand menu (QuickLaunch) being ignored unless the link is clicked twice. This is quite similar to an error we had some months ago #3168 When the link is clicked, the URL updates but the original content is rendered. We're not seeing our React didMount or render functions getting called.

Steps to reproduce

Add a page and set it to SinglePageWebPart. Add an SPFX component.
Create another page
Click the first page - its content will render
Click the second page - the URL changes but the content remains the same
Click either link twice and it forces a reload and the full content is there.

Adding another page without seeing it to SinglePageWebPart - navigation between the two page types works as expected.

Expected behavior

Page content to update

Developer environment

SPFX 1.09 and 1.10 have the same issue

[msft-github-bot]

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[andrewconnell]

@GrahamMcMynn Is this related to the navigation events?

[ng-marcus]

(I think you can ignore this double call, as this happens on tenancies where it still works)

This may be related (and I only looked because this was the issue last time) but when the page loads, it makes two calls to get the page json . (the page is Contacts.aspx here)

Both are GET calls

The second response has no response body.

[GrahamMcMynn]

@andrewconnell - I don't believe it is, however, I will take a look and try reproducing it.

[ng-marcus]

If it would help with analysis if you would like access to our Dev tenancy let me know and I can create a user account for you.

[patmill]

Sorry for going dark @ng-marcus . We have made a series of fixes on the page->page navigation flows over the past while. Is this still an issue for you?

[ng-marcus]

Hi @patmill Thanks for checking in. I'll get the team to test and get back to you tomorrow. We added a work around that fully loaded the page each time, so we will disable that and see how it works now.

[ng-marcus]

Hi @patmill We still see the same problem sorry. With Single Page Apps we still have the issue where the user has to click twice on a navigation link to make the content change.

[patmill]

Thanks @ng-marcus - we're looking into this.

[AJIXuMuK]

This should be WW now.

[ghost]

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues