Forum Discussion
Please help! ALL Modern pages impacted | SharePoint spacing issue
Gayatri Ohri - word from engineering is they are rolling back our last update; should be fixed for most tenants now. Thanks again for eyeballs and calling to attention. - Mark
- Gayatri OhriNov 09, 2020Brass Contributor
Mark-Kashman - Thanks for your reply.
The issue has now come up in another area. The space under the Hero web part is now increased to 24px. I think they restored the missing space and added this extra space below the Hero.
Find attached the screenshot.
Please help with this issue. There is way too much space. Again it is not visible on edit mode and only appears after publishing.
HERE is the CSS causing the issue:
@media screen and (min-width: 641px) .CanvasComponent.LCS .CanvasSection--read.RestoreLostMargin .ControlZone:last-of-type { margin-bottom: 24px; }
- Gayatri OhriNov 10, 2020Brass Contributor
Mark-Kashman - Do we have an update on this new change that has been made?
- Martin-CoupalNov 06, 2020Iron Contributor
Mark-Kashman , I totally agree with Rafael Garcia . It is clear there is an issue with code testing and release at Microsoft. Also, when we open tickets to inform Microsoft about issues, we are being ask to do the testing to replicate the issue even if the issue is global. As an independant consultant I'm wasting hours almost every weeks with tickets and loosing billing hours as I want to be fair with my customers and not charge them for bugs released by Microsoft... Microsoft should not rely on their customers to do the testing for them. Hope Microsoft is taking this seriously and will take action.
- Rafael GarciaNov 06, 2020Copper Contributor
As usual, no apologies no explanations.
About 2 weeks ago the padding between columns changed (from 8px to 24px) and then it was rolled-back some days later. Now the padding between webparts changes...
How can these things happen and what are you going to do to stop happening? All these changes and rollbacks create the sensation of an unstable product.
What kind of quality assurance you have? No developers or testers noticed this very visual issue? Really? Maybe you need to review your procedures (if any).
Finally, why this change was released to everybody and not the targeted release tenants only?