history.replaceState API method is not working as expectedIssue The standard web API history.replaceState method is no longer working as expected..Previously in Tokyo and earlier release it was. ReleaseUtah and aboveCauseThis is expected behavior.ResolutionUntil Tokyo, the service portal page HTML does not contain the '<base>' tag. Starting in Utah and above, as part of a change to make service portal URLs more human readable, <base> tags were introduced that have the href value the same as the portal suffix like <base href="/<portal-suffix>" >. Hence, the URL to be used in the replaceState API should be everything after the <base> tag. Eg. history.replaceState( {} , '', '?id=sc_category#tab=t1' ); Related LinksStarting with the Utah release, as part of improving SEO, Portal pages are made to be configured for human-readable URLs. Eg. earlier URLs looked like "<instance-url>/sp?id=kb_article_view&sys_id=471ee81eff6002009b20ffffffffff34". But now the same URL can be configured to look like "<instance-url>/sp/en/getting-around-in-windows?id=kb_article_view&sys_id=471ee81eff6002009b20ffffffffff34"More info can be found here https://docs.servicenow.com/bundle/utah-servicenow-platform/page/product/knowledge-management/task/add-human-readable-keywords-knowledge-pages.html1. Is it possible to deactivate the <base> tag feature?There is no OOB functionality to de-active the <base> tag, and it is not recommended to remove the <base> tag.2. Is there a reason why ServiceNow decided to add the <base> tag?<base> HTML tag is an industry standard and can be used as per the need. - documentation can be found here: -https://developer.mozilla.org/en-US/docs/Web/HTML/Element/base3. Does removing the <base> tag impact anything ?Yes - it impacts the portal navigation for the portal pages with human-readable URLs configured and URLs with language path parameters like /sp/en