Sp-dev-docs: View Formatting schema - hideColumnHeaders function stopped work listview webpart

[amazinjoey]

Category

• [ ] Question
• [ ] Typo
• [ ] Additional article idea
• [x] Bug

Question

It seems that the hideColumnHeaders function has decided to stop working in list view webpart. So the flag 'true' does nothing. It was working fine until friday.

Environment details (if applicable)

SharePoint Online

[msft-github-bot]

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

[PrasadKasireddy]

Related issue - https://github.com/SharePoint/sp-dev-list-formatting/issues/123
https://github.com/SharePoint/sp-dev-docs/issues/5213

[shagra-ms]

Thank you for reporting this. The issue has been identified and fixed. Fix would be rolled out in upcoming updates.

[furler]

Thank you for reporting this. The issue has been identified and fixed. Fix would be rolled out in upcoming updates.

Does the fix also include the related issue of "flexbox like" tiles staggering when embedded on a page via the list view web part? Multiple posts have been created for this recurring issue, I think the one @PrasadKasireddy posted: https://github.com/SharePoint/sp-dev-list-formatting/issues/123 being one of the first.

Note again this has nothing to do with the new tileProps property, which doesn't work at all when lists are embedded because you can't specify the tile view as the default view in the list web part.

Thanks,

[shagra-ms]

Yes the 'flexbox like' tiles staggering will also be fixed with this fix. Though the fix on the list web part is a bit delayed and would roll out in 2-3 weeks.

We take your feedback on tileProps, and are now tracking this in our backlog.

[coupalm]

2 to 3 weeks before the fix gets applied is very long. Is there anything that can be done to speed that up?
Thanks!

[PrasadKasireddy]

Duplicate of #5281

[shagra-ms]

The fix is now available in production tenants.

[msft-github-bot]

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