Forum Discussion
Modern site home page focus is not at the top of the page
When I open up any SharePoint modern site home page to start off with you see the top of the page but then almost immediately the page automatically scrolls down so the focus is at the middle or bottom of the page.
I have set my pages up so that the News stories are at the top of the home page so users can always see the news first. However the focus of the page is scrolling past the news so you see the middle or bottom of the page.
This is happening on both pc and mobile access.
How to I make sure that when a user opens a site and the home page opens the focus is at the top of the page.
Thanks
- Can't say I've ever seen this happen before, are you using a custom URL to access the site etc.? What if you manually type your URL in from another browser or in-private browser does it do the same?
Going to assume no custom SPFX Application Extensions have been installed that might be injecting code into this site as well?
54 Replies
We are also experiencing this issue but the problem is that the page auto focuses to an embed web part which I am using to display an O365 calendar.
Same on our page as well. We've got a Newsfeed there and it always jumps to the bottom of the newsfeed box, which basically is the end of the page.
I've reduced now the size/length of the newsfeed, so it matches the length of the other column of the page and I was certain that on another SharePoint page I've seen a setting to configure this behaviour, but I can't find it again. :(
Any news from MS side or anybody found a solution yet?
To delete this newsfeed from the page is not a valid solution to my mind.
I'm seeing the same issue with a page that has the newsfeed lower down. When you navigate to the page it jumps to the news. Is there still no real fix for this other than moving the webpart?
Just confirming the fix that MS rolled out to all tenants also addressed the issue at hand within our environment.
Confirmed fix. It Works on our page Again. (Y)
Rock on MS - good credit when they fix and respond. See you at Ignite
I have confirmed that this has been fixed for our Tenant as well. Thank you everyone for sharing your info!
Just seen that it's been fixed on our sites as well.
Looks like this issue is fixed on the tenant we are on - hope the same for you!
- I have the same issue with the News web part at the top of the page. Does it focus on the Hero web part?
That's interesting...I was doing further testing this morning and it does not appear to be an issue with the Hero Slider web part...which I also had suspicions of when the issue started. I tested a page that had both the Hero Slider and Document Library web parts...and as soon as I removed the Document Library web part...the issue went away.
As far as I can tell, this issue revolves around two web part types. Document Library and List. Hero has not affected my tenancy.
I was in contact with Microsoft. They found the bug :-) ETA for release in production would be in 2-3 weeks.
Cheers
Bernd
Agility, let's see how many days 2 to 3 weeks are for Microsoft ... ;-)
- It's 2023 and I'm still having this problem, so 2-3 weeks seems to be 4+ years
The issue seems to be have been resolved within our tenant and here is the unofficial response from MS:
“Flight has been disabled for this and customer is no longer facing this issue. Customer had set himself to first release target in his subscription.. That's why some of the new features had affected his tenant..
He can set himself to standard release option in his subscription”
Hope this helps anyone else that has experienced the issue at hand.
Also not sure where you set the release target.
Gosh, I wish - I am still having the focus issue. I may try putting in the webpart vs the library / list, as suggested by a previous response - I will report back. Grazie!
Came in to the office today and sure enough...the issue is now back...I'm exchanging emails with MS right now and have escalated the ticket again...hoping to get something back from MS regarding what occurred on Friday that fixed the issue and now on Monday...the issue is reappearing tenant wide...
