Reply to thread

I've spent some time trying to debug this and unfortunately I'm not able to identify the specific cause. It is editor related, but it does get triggered if the editor has been disabled on the page (but not if it was disabled and not loaded). At this point, I'd have to guess that the system for focusing the editor's iframe is triggering it, combined with a bug that doesn't ignore it when the iframe is hidden, but I'm not totally clear. This is deep within the OEM-specific code as programmatically focusing via JS doesn't appear to have any issues.

Unfortunately, identifying the devices in question by user agent is very tricky. There may be a model number in some cases, though there are a huge number of applicable model numbers and variations.

This is going to have to be considered a browser issue for now.