New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firefox XML Parser Iframe not working #86
Comments
This URL is on a secondary domain I operate. The only difference is that the page is served as application/xhtml+xml and there is an XML declaration. The PHP code otherwise calls all the exact same code. Again, this only breaks in Firefox and there is the error in the console, "Error: Permission denied to access property "sq-card-number-iframe""
This bug forces me to load the form in an iframe / prevents me from being able to implement the form directly. Could I please get some insight in to any action to resolve this bug? About the only difference between the HTML and XML parsers is that you should use To clarify, this issue is about the iframes not loading using the XML parser in Gecko browsers (e.g. Firefox, Waterfox), not about submitting the form. |
Hi @jabcreations we recently deployed a change that should resolve issues with the XHTML content type, and should eliminate the need for workarounds. |
I love it! Thank you! I am curious, what was (or were) the issues that prevented the XML parser from working in Gecko/Firefox? |
Hi @jabcreations the issue boiled down to minor DOM API differences in Firefox when the content type is |
For now I've gone the cheap route and am sticking the form in an
iframe
element though it does make my code much more convoluted and I am unable to properly integrate the credit cardiframe
elements in to my code properly. IE and Chrome display theiframe
elements just fine.I code everything in XHTML5 now (HTML5 + XML parser). I prefer the XML parser because it's strict and will spawn error messages if I get sloppy. The Gecko rendering engine (Firefox though I'm forced to migrate to Waterfox due to Mozilla committing suicide come mid-November) handles XML errors best.
The fourth line in the code below sends the XML parse header. If you comment it out when testing Firefox will work however I can not degrade my entire platform because of such a specific bug.
I'm not sure why this bug is triggering. It happens on both local and live test environments (e.g. 127.0.0.1, localhost and example.com). There seems to be some issue popping up in the web console. If you guys need any additional information please let me know.
The code below is the same found on this page however I've attempted to minimize it while still keeping it reasonable readable.
The text was updated successfully, but these errors were encountered: