When will Mozilla finally fix that bug that doesn't pass "Origin" in the Ajax header when POSTing to an API with JSON?
Hello, y'all. I love that I can perform a CORS Ajax POST to my API, but alas in Firefox for Android (Gecko/68), it is the only browser in existence that won't send the "O…
Hello, y'all. I love that I can perform a CORS Ajax POST to my API, but alas in Firefox for Android (Gecko/68), it is the only browser in existence that won't send the "Origin" in the header to my server, and causes my CORS call to die a miserable death. Even the desktop version of Firefox allows this, and I had no problems with Chrome, Mobile Chrome, Safari, IE, Edge, Opera... Why so stingy? I found a 9 year old thread talking about how developers kept going back and forth with this over some security issue (mainly pre-stating the origin manually in the header, or some sort of spoofing), but this seems like a real no-brainer here. Can anybody explain why I now have to exclude Firefox for Android as a useful browser to view this app?
I'm trying to debug a site that doesn't show up properly in Firefox for Android. Specifically, we're using wavedrom to render fields, and they work fine on Desktop, but …
I'm trying to debug a site that doesn't show up properly in Firefox for Android. Specifically, we're using wavedrom to render fields, and they work fine on Desktop, but Android doesn't work.
The closest I've gotten is https://developer.mozilla.org/en-US/docs/Tools/about:debugging, which is very similar to the previous article. Note that the network debugging doesn't work. I can see devices over USB, and I can try connecting to a particular tab, however doing so gives me the error "typeerror this.topwindow is null".
I'm running the latest version of Firefox for Android, which is 68.6.0. My desktop browser says "The minimum supported version is (72.0a1)." However, there is no such version.
How can I see the console output?
I just want to get the console output. Is there any