Skip to content

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

Closed
1 of 4 tasks
estruyf opened this issue Jan 23, 2018 · 7 comments
Closed
1 of 4 tasks

Placeholders not always available for application customizers #1265

estruyf opened this issue Jan 23, 2018 · 7 comments
Labels
area:spfx Category: SharePoint Framework (not extensions related) status:tracked Currently tracked with Microsoft’s internal issue tracking system. DO NOT ADD/REMOVE (MSFT managed) type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.

Comments

@estruyf
Copy link
Collaborator

estruyf commented Jan 23, 2018

Category

  • Question
  • Typo
  • Bug
  • Additional article idea

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.

large gif 1156x720

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

@VesaJuvonen VesaJuvonen added type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs. area:spfx Category: SharePoint Framework (not extensions related) status:tracked Currently tracked with Microsoft’s internal issue tracking system. DO NOT ADD/REMOVE (MSFT managed) labels Jan 25, 2018
@VesaJuvonen
Copy link
Contributor

Potential duplicate of #1254 and #1263. We'll investigate on engineering side.

@VelinGeorgiev
Copy link
Contributor

VelinGeorgiev commented Feb 8, 2018

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

@ahackettms
Copy link

@estruyf @VelinGeorgiev : Are you still experiencing this issue? Could you please help check again?
We had some fixes recently which may have fixed this.
Thanks

@ahackettms
Copy link

We have fixed this issue. Please let us know if this is still an issue. Closing

@VelinGeorgiev
Copy link
Contributor

Thanks @ahackettms , I will test and let you know if any issues.

@VelinGeorgiev
Copy link
Contributor

@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.

@msft-github-bot
Copy link
Collaborator

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

@SharePoint SharePoint locked as resolved and limited conversation to collaborators Jan 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area:spfx Category: SharePoint Framework (not extensions related) status:tracked Currently tracked with Microsoft’s internal issue tracking system. DO NOT ADD/REMOVE (MSFT managed) type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.
Projects
None yet
Development

No branches or pull requests

5 participants