When I export an HTML5 ad I can click through the ad but the cursor changes to a pointer for only a half second and changes back to a pointer. This happens on Mac and PC. My client and the ad network is saying the same thing. Am I missing something?
728x90-chicago.zip (119.2 KB) 728x90-chicago.hype.zip (128.5 KB)
Hi @starflyer
Did you mean?:
but the cursor changes to a hand pointer for only a half second and changes back to a pointer
It stays as hand pointer for me, without reverting to a normal pointer. (Tested on Chrome, Safari, Firefox, Edge and Firefox Developer Edition - all on MacOS though)
I had to run it on MAMP for the click to work though as I was getting CORS error due to linking to ds.serving-sys.com/BurstingScript/EBLoader.js. I assume this is due to the ad network?
Are you testing it locally only, without uploading to a testing server? Did you check the console for issues? These show on mine:
A parser-blocking, cross site (i.e. different eTLD+1) script, http://ds.serving-sys.com/BurstingScript/EBLoader.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message. See https://www.chromestatus.com/feature/5718547946799104 for more details.
[Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
Also, you might want to uncheck Allow text selection on all elements and and check Ignore all pointer events on all except the top button.
Could you perhaps provide more concrete steps to reproduce (at least what browser/OS and versions you are using)? A video would be great. Does this happen when all other apps and browser windows/tabs are closed?
We’ve definitely gotten other reports of similar behavior over time but haven’t had enough live cases to fully figure out might be happening. The best I can tell from right now is that it is more of a browser bug or perhaps content on other apps is manipulating the cursor, but it is premature to fully say.