-
-
Save cramforce/63a8f25639b0201a7c48c90f7a4e1eba to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| We are seeing this Firefox bug (or a variant of it) get triggered https://bugzilla.mozilla.org/show_bug.cgi?id=548397 | |
| This showed up in our error reporting and the stack trace format is clearly a Gecko stack trace. | |
| Example URL https://m-wikihow-com.cdn.ampproject.org/v/m.wikihow.com/Dress-for-Skiing?amp=1&_js_v=7 embedded as an iframe on https://www.google.com | |
| The UAs are sometimes: | |
| Mozilla/5.0 (Linux; Android 6.0.1; SAMSUNG SM-G920F Build/MMB29K) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/4.0 Chrome/44.0.2403.133 Mobile Safari/537.36" | |
| And more often: | |
| Mozilla/5.0 (iPhone; CPU iPhone OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13B143 Safari/601.1" |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The reason why we know it is Firefox is because the error report we receive uses Firefox's stack trace format, which is distinctly different from Chrome and WebKit. We don't really have an immediate problem. The issue is clear in terms of how we can fix it (although we might have found a new bug in Firefox), we were just wondering why we see these UAs, as that drove our debugging session into the wrong direction.