When browsing items from the search, it was discovered in hindsight that the same item pages work as expected, but when clicking on an item that is displayed as a "similar sponsored items" and opens a new tab, the newly opened tab page would load the page visually but then hang for a 5-10 seconds where I am unable to click on anything, nor will moussing over the images provide any responsive zoom.
I am, however, during that time, able to scroll the page the page and noted that Chrome shows the page still loading during the hang. Since the page is unresponsive to mouse clicks or mouse hovers, I used F12 to open the debugger but that also won't open until the page escapes from the hang. At which point, Chrome no longer shows a loading wheel next to the tab name.
I checked the item page by copying and pasting the same URL using an incognito browser in case it was one of my extensions but the behavior is the same. Using Chome Version 104.0.5112.81 (Official Build) (64-bit).
Below is the referenced & witnessed error reported by the console:
Refused to execute inline script because it violates the following Content Security Policy directive: "script-src http://*.ebaystatic.com https://*.ebaystatic.com http://*.ebay.com https://*.ebay.com". Either the 'unsafe-inline' keyword, a hash ('sha256-KhWpqX28wg9Oe4I7/B5zY6WXIfJjaigG6U9D41brnqc='), or a nonce ('nonce-...') is required to enable inline execution.
Although the console does report other errors after the page un-hangs, the message above seems to be related to eBayISAPI.dll
Since it was not discovered or realized until during my time posting this, I suspect it may be related to the tracking scripts for sponsored items? Though I'm just speculating and lack any expertise in web development. But, in conjunction and in case it's worth noting, I do have the setting for third party cookies to be blocked in my browser settings, however when checking for cookies on the page, no blocked cookies appear in the list:
A similar error message was previously reported by another user here but the issue is a bit different and relate to not checking a box for making an address the default address so I may I'm not sure if it may necessarily be related to the cookies speculation.
It's recognized my less than savvy tech opinion may not be of any use and I will henceforth refrain.
