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.

Sign up for GitHub

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

Fix issues related to new semantics of XML namspacing in Chrome #1125

Open

michael opened this issue Sep 12, 2017 · 0 comments

Member

michael commented Sep 12, 2017

As reported by Danne from Infomaker:

It seems the problem stems from version 61.0.3163.79 of Chrome. This change
in testing code accurately describes the previous behaviour and the new behaviour:
https://chromium.googlesource.com/chromium/src/+/758742204e186ac83e73b4a393bdfaa660e2ca15%5E%21/#F0

The relevant section in the W3C Namespaces recommendation
https://www.w3.org/TR/xml-names/#defaulting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment