Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

XHR post blocked when Captcha is selected

  • 2 wotmołwje
  • 0 ma tutón problem
  • 1 napohlad
  • Poslednja wotmołwa wot spliffys

more options

Hello, I am struggling with a bug specific to Firefox (108.0.2) in which I have an XHR Post that is being blocked by dev tools only when a google captcha is selected. Here is the website that the bug is happening on. Per comment suggestions I've added a screen shot of the URL being blocked in dev tools.

My overall goal is to have this form post it's action and post the form data to another endpoint (https://beeceptor.com/console/preferencecenter). I am able to successfully post data to beeceptor with the captcha selected when testing in Chrome, but as stated not Firefox. If the form is submitted without the captcha selected the data is successfully posting to the beeceptor endpoint- this behavior is happening with both Chrome and Firefox which I am sure means something is wrong with my Javascript which can be resolved later.

Looking at the console in Firefox I am consistently seeing a XHR Post blocked to the beeceptor url with captcha selected. I have gone through several iterations of this code to resolve the issue, none of which have successfully worked. After many, many, hours of digging I have done the following to no avail.

  • Cleared Cache
  • Ran in Safemode then back to regular mode (one article this appeared to fix for a user)
  • Ran in Private Browsing
  • Adjusted CORS accordingly

There are more items I've attempted that I can't remember off the top of my head.

Any help with this would be greatly appreciated as I have hit a wall.

Hello, I am struggling with a bug specific to Firefox (108.0.2) in which I have an XHR Post that is being blocked by dev tools only when a google captcha is selected. [https://www.pages09.net/grandamericahotelsandresorts/DEV-SBSFDCPrefCenter/Preference_Center/ Here is the website] that the bug is happening on. Per comment suggestions I've added a screen shot of the URL being blocked in dev tools. My overall goal is to have this form post it's action and post the form data to another endpoint (https://beeceptor.com/console/preferencecenter). I am able to successfully post data to beeceptor with the captcha selected when testing in Chrome, but as stated not Firefox. If the form is submitted without the captcha selected the data is successfully posting to the beeceptor endpoint- this behavior is happening with both Chrome and Firefox which I am sure means something is wrong with my Javascript which can be resolved later. Looking at the console in Firefox I am consistently seeing a XHR Post blocked to the beeceptor url with captcha selected. I have gone through several iterations of this code to resolve the issue, none of which have successfully worked. After many, many, hours of digging I have done the following to no avail. * Cleared Cache * Ran in Safemode then back to regular mode (one article this appeared to fix for a user) * Ran in Private Browsing * Adjusted CORS accordingly There are more items I've attempted that I can't remember off the top of my head. Any help with this would be greatly appreciated as I have hit a wall.
Připowěsnjene fota wobrazowki

Wot spliffys změnjeny

Wubrane rozrisanje

I found the root issue of this to be stemming form jquery's validate plugin. Cleaning up the javascript resolved this issue. Hopefully this helps someone else in the future.

Tutu wotmołwu w konteksće čitać 👍 0

Wšě wotmołwy (2)

more options

Thanks Dropa, I've included a screen shot with the original question now.

more options

Wubrane rozrisanje

I found the root issue of this to be stemming form jquery's validate plugin. Cleaning up the javascript resolved this issue. Hopefully this helps someone else in the future.