🙏 Extensions: Application Customizer - Additional Placeholders Requested

[andrewconnell]

Category

• Question
• Typo
• Bug
• Additional article idea

Today we get PageHead & PageFooter... would like to have BEFORE/AFTER DIV's for QuickLaunch & PlaceHolderMain

If you are planning to share a new feature request (enhancement / suggestion), please use SP Dev UserVoice at http://aka.ms/sp-dev-uservoice.

OK... cross-referenced:
https://sharepoint.uservoice.com/forums/329220-sharepoint-dev-platform/suggestions/19536022-extensions-application-customizer-additional-pl

[VesaJuvonen]

Thx AC for the input.
We'll absolutely introduce additional placeholders for the framework and this is a good input for getting the needed placeholders tracked. We would also love to have some details around the actual scenarios where you'd use the requested capabilities. That might be obvious in some cases, but actual business scenarios and use cases help to prioritize the requests. Thx.

[patmill]

Cross posting my response from UV.

Hey AC - While I know what you mean here, can you refine this to target the modern experiences? For example, PlaceholderMain is an asp.net masterpage div that doesn't exist in the newer code. Would you think of Pre/Post Placeholdermain to be ContentHeader and ContentFooter (as opposed to PageHeader and PageFooter?

Additionally, how would you expect scrolling to work in this scenario? For example - what should happen with a listview with infinite scroll vs. a page with 500k of text?

[andrewconnell]

@patmill Will xpost from UV too :)
Specifically looking for any place these extensions are supported... if that's just modern experiences, then just those (although I hope these will also apply to classic pages, just as client-side web parts do). Understand the names are different... I was referring to the intent of where things would go... a picture might help. I see the RED is what you provide today... the GREEN is what I'm asking for:

As for infinite scroll... I'd expect it to behave like the components that wrap them. For instance, on the QuickLaunch, it doesn't scroll so I'd expect what I put right after it to be pinned to the bottom border of the QL. Same is true with the main body of the page.

@VesaJuvonen - Biz case: context help, messages to the user based on the context of what they are doing or reminders they haven't done something. I could do this by doing DOM manipulation from the header / footer, and that's what folks will do as these are common places we want to add / remove stuff... but that's now how we should be doing it... so don't give them a reason to do it and add it for them. Make sense?

[PopWarner]

I agree with AC. While @VesaJuvonen has mentioned that keeping our customization's within the confines of these placeholders, which I assume is the contractual safe place for custom content, ensures that it will not get destroyed or broken with future updates to the DOM, if there are not additional Placeholders to be populated, users will simply begin manipulating the DOM.

While this isn't how they should add customization's, as @andrewconnell as mentioned, if there are no other places, peeps will still do it.

The Pre/Post locations could also provide the ability to wrap that content with a custom CSS classname for ensuring specificity within a certain brand/design.....just one possible other thought.

Adding some additional placeholder requests here, as discussed in #656

1. Site metadata: custom site meta data (state, contacts, project duration...)
2. Search bar: custom search bar
3. Left navigation: having a global navigation, buttons to create documents from templates, showing company's applications...

[lucaband]

To updated everyone on this topic: the scenario is well understood and we are working to be sure we tackle that properly. There's still an open conversation to understand if Placeholders is the right technology to use to enable such scenarios or it is something else.

[andrewconnell]

I'm confused @lucaband ... why close the issue if the conversation is still open even if internally?

[lucaband]

Andrew, thanks,
Reason why I closed was because I though I answered the initial question.
But I'm perfectly fine to keep it open, assign it to me, and reply back here once we have some concrete news.