How do you get rid of the default scroll bars on service portal?

[gregholcomb]

These vertical and horizontal scroll bars always appear when using Google Chrome as the browser.   My page ends up having two vertical scrollbars and one ineffectual horizontal scrollbar.   I am using the Istanbul version.   Any way to disable this?

Edit:   Originally I was under the impression that it was only Google Chrome that had the issue with the embedded scroll bars, but as I checked on other browsers (Firefox and Internet Explorer), I noticed that they all have a problem, Internet Explorer being the worst of the three.   With Internet Explorer, the vertical scroll bars are stacked on top of each other.   I am using Windows 10 and all of my browsers are up-to-date.   Below are some screen captures for clarity.

Google Chrome

Firefox

Internet Explorer

[_Gaurav]

Hello @RobKnox @tim_treacy 
I hope you're well and doing good.
Did you find anything regarding this issue? I am also experiencing the same problem and it isn't very pleasant.
Current chrome version is: 131.0.6778.70 (Official Build) (64-bit)

[Ramiro4]

Hi All,

Servicenow has updated us with the next investigation summary: 
They have come across with few similar issues which were getting caused by the 'Grammarly' installed on their system. Their proposal is to check if Grammarly is installed, if so, try to disable it to see if it resolves the issue. 

[RobKnox]

Hi Ramiro4, Thanks for the update. I can confirm that disabling the Grammarly plugin stops the issue. However, it does make my communication with our customers incoherent, LOL. 😉

It actually now makes sense as the issue does not start on a page until you place your cursor in a text box field in which the Grammarly plugin is active.

---Rob

[_Gaurav]

Hi @Ramiro4 thanks for the quick response.

I did tried removing the Grammarly extension from the chrome and it seems like the issue is no longer exists in the systme for me.

Thanks!

[tim_treacy]

Ramiro4, 

We've also had conformation that the issue was being caused by the Grammarly browser extension, and that disabling/removing it, addressed the issue.