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
Although empty target name isnot allowed, we would check that (or change parsing)
the same way as currently we check the presence of mandatory `version` attribute
in XML declaration. This requires introducing separate type for PI content which
will be done in tafia#650
Fixed (3):
syntax::pi::normal_empty::async_tokio
syntax::pi::normal_empty::borrowed
syntax::pi::normal_empty::buffered
failures (3):
syntax::decl::normal1::async_tokio
syntax::decl::normal1::borrowed
syntax::decl::normal1::buffered
Although empty target name isnot allowed, we would check that (or change parsing)
the same way as currently we check the presence of mandatory `version` attribute
in XML declaration. This requires introducing separate type for PI content which
will be done in tafia#650
Fixed (3):
syntax::pi::normal_empty::async_tokio
syntax::pi::normal_empty::borrowed
syntax::pi::normal_empty::buffered
failures (3):
syntax::decl::normal1::async_tokio
syntax::decl::normal1::borrowed
syntax::decl::normal1::buffered
Currently we use
BytesText
for them, but this is a text that represents a text with character and entity references, but that references MUST NOT be recognized within processing instructions.The text was updated successfully, but these errors were encountered: