Skip to content
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

No signalling of end-namespace-binding #14

Open
laurie71 opened this issue Feb 8, 2011 · 0 comments
Open

No signalling of end-namespace-binding #14

laurie71 opened this issue Feb 8, 2011 · 0 comments

Comments

@laurie71
Copy link

laurie71 commented Feb 8, 2011

onStartElementNS() passes an array of namespace prefix/uri pairs, signalling the start of a namespace binding, but onEndElementNS() has no corresponding callback parameters to signal when namespace bindings go out of scope. This makes it necessary for API clients to implement a stack/counter pair to match end-element callbacks to start-element callbacks that introduced new namespace bindings, in order to correctly interpret common patterns of usage of prefixes on attribute names and within attribute values.

The recommended solution would be to add onStartNamespace and onEndNamespace callbacks, and remove/deprecate the 'namespaces' callback argument to onStartElementNS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant