sp-dev-docs icon indicating copy to clipboard operation
sp-dev-docs copied to clipboard

App page property pane follows navigation into unrelated webparts

Open Drenam1 opened this issue 8 months ago • 9 comments

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

šŸ’„ SharePoint Framework

Developer environment

Windows

What browser(s) / client(s) have you tested

  • [ ] šŸ’„ Internet Explorer
  • [x] šŸ’„ Microsoft Edge
  • [x] šŸ’„ Google Chrome
  • [ ] šŸ’„ FireFox
  • [ ] šŸ’„ Safari
  • [ ] mobile (iOS/iPadOS)
  • [ ] mobile (Android)
  • [ ] not applicable
  • [ ] other (enter in the "Additional environment details" area below)

Additional environment details

Chrome Version 135.0.7049.115 (Official Build) (64-bit) SPFx version 1.18.0 Node.js version 18.20.4

Describe the bug / error

If you open the property panel on an App page with an SPFx webpart, then close it (or leave it open) and navigate to another page with webparts (custom or out-of-the-box), the App page title and header will appear in the property panel for any webparts edited.

Steps to reproduce

  1. Navigate to an App page with a full-page app.
  2. Edit the App page to see the property panel. Close it without changes, leave it open, etc - it makes no difference.
  3. Without refreshing, navigate to another page with webparts.
  4. Edit the page and open the property panels for some webparts. You will see the App page title and the header at the top of the property panel. This happens for both custom and MSFT webparts.
  5. If you refresh the page, this behaviour disappears.

https://github.com/user-attachments/assets/f8d79263-dd18-4c84-bc40-20de012d8dd4

Expected behavior

When you open the property panel for a webpart, you should only see properties for that webpart not for previously opened webparts.

Drenam1 avatar May 12 '25 14:05 Drenam1

Hello @Drenam1, Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

Ashlesha-MSFT avatar May 13 '25 04:05 Ashlesha-MSFT

@Drenam1, I’m trying to reproduce the issue, but I’m not seeing any web parts when editing the page where I added the app. Could you please clarify the steps a bit more? Also, if possible, could you please share the SPFx solution or an example App page setup so I can test it accurately?

Image

Ashlesha-MSFT avatar May 13 '25 07:05 Ashlesha-MSFT

The initial app (in steps 1-2 of my instructions) needs to be a full-page SPFx webpart, configured with SharePointFullPage as its supported host like in this article. The webpart then gets added to the page via New > Page > Apps

Image Image

There are no out-of-the-box webparts like this as far as I know - however, any of the SharePointFullPage SPFx sample webparts should work for reproduction purposes.

Drenam1 avatar May 13 '25 11:05 Drenam1

@Drenam1, Doing the same, to test.

I was able to reproduce the issue only once, and that was the first time I published the page. After several refreshes, I could no longer reproduce it.

Ashlesha-MSFT avatar May 16 '25 11:05 Ashlesha-MSFT

@Drenam1, Doing the same, to test.

I was able to reproduce the issue only once, and that was the first time I published the page. After several refreshes, I could no longer reproduce it.

Strange... it happens for me every time I go from editing an app page and saving, then navigating to a normal page

Drenam1 avatar May 16 '25 11:05 Drenam1

Just following up to see if you're still experiencing the issue with the App page property pane showing up on unrelated web parts.

Ashlesha-MSFT avatar Jul 18 '25 12:07 Ashlesha-MSFT

@Ashlesha-MSFT Yes this is still happening

Drenam1 avatar Jul 21 '25 09:07 Drenam1

@Drenam1, Thank you for your continued support and follow-up on this.

After further investigation and repeated testing (about 5–6 times), I was able to consistently reproduce the issue as originally described. It seems to occur reliably under the stated conditions when navigating from an App page with a full-page SPFx webpart to a regular page with other webparts, without refreshing the browser.

We will go ahead and create an internal bug for this so that the engineering team can take a closer look.

Apologies for the earlier misinterpretation and the delay in response. Appreciate your patience and help in tracking this down.

Image

Ashlesha-MSFT avatar Jul 23 '25 09:07 Ashlesha-MSFT

Hello, I wanted to follow up and ask if there have been any developments regarding this issue

Rafaelki avatar Oct 22 '25 11:10 Rafaelki