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

AttributeList.set(int,Attribute) may have false positive Namespace Collision issue #90

Closed
rolfl opened this Issue Aug 27, 2012 · 0 comments

Comments

Projects
None yet
1 participant
@rolfl
Collaborator

rolfl commented Aug 27, 2012

Namespace collision happens when the new Attribute will require two different namespace URLs wit the same prefix to be in scope for an Element. Setting an attribute position to a new attribute may cause a namespace collision if the new attribute has the same prefix, but different URL, as an existing item in the Element.

But, if the only collision is with the attribute that is being replaced, then there is no collision.... but the current checkNamespaceCollision does not take the replaceing-the-collision-attribute in to consideration, and it should.

@rolfl rolfl closed this in 500f9e5 Sep 2, 2012

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