You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we should provide an equally convenient way to access the error reason string and XML element name (this would also work for the XML processing instruction target). For the XML element name case, it should be an lvalue.
At least in the XML case, it is reasonable to think of the XML element name as being a special unnamed attribute, which suggests using E._ as the syntax.
The text was updated successfully, but these errors were encountered:
Assuming we change errors to use branding (#413, #459), then this will apply only to XML elements and processing instructions.
jclark
changed the title
Provide convenient access to error reason string and XML element name
Provide convenient access to XML element name
Mar 25, 2020
Assuming
we should provide an equally convenient way to access the error reason string and XML element name (this would also work for the XML processing instruction target). For the XML element name case, it should be an lvalue.
At least in the XML case, it is reasonable to think of the XML element name as being a special unnamed attribute, which suggests using
E._
as the syntax.The text was updated successfully, but these errors were encountered: