-
Notifications
You must be signed in to change notification settings - Fork 1k
Placeholders not always available for application customizers #1265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I experience similar behavior. Not just the app customizer, but also any custom webparts are not loaded along with the customizers. Adding reference to my issue here: #1309 |
@estruyf @VelinGeorgiev : Are you still experiencing this issue? Could you please help check again? |
We have fixed this issue. Please let us know if this is still an issue. Closing |
Thanks @ahackettms , I will test and let you know if any issues. |
@ahackettms , I can confirm that that one can be closed. However you still have problems with the customizer and page transitioning. Please have a look at the new issue: #1464. |
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 |
Category
Expected or Desired Behavior
When creating an application customizer that shows a header or footer, the expected behavior should be that it is loaded on every modern page.
Observed Behavior
When navigating to document or pages libraries, it occurs that the top and bottom placeholders are not available. When page if completely refreshed, they appear again.
At the end of the GIF you see
1, 2
printed. This is the output of:this.context.placeholderProvider.placeholderNames.join(',')
, but this does not occur on first page navigation.Steps to Reproduce
I tried this by following the guide: https://docs.microsoft.com/en-us/sharepoint/dev/spfx/extensions/get-started/using-page-placeholder-with-extensions
The text was updated successfully, but these errors were encountered: