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
{{ message }}
This repository has been archived by the owner on Jul 28, 2023. It is now read-only.
We've found a couple of sites that have xpacket sections: talsunovads.lv and hlz.de.
Checking the nodeType, it seems they are considered nodeType 7. As we are not handling that use case, it returns an error: TypeError: Cannot read properties of undefined (reading 'length').
We have to decide what to do with these nodes. Should we do the same as with CDATA nodes? It seems a similar case, as they are included inside the SVGs.
The text was updated successfully, but these errors were encountered:
Should we do the same as with CDATA nodes? It seems a similar case, as they are included inside the SVGs.
It's a similar case indeed, but I think we should remove them in this case like we are doing with comments.
To be honest, I don't fully understand how browsers handle Processing Instruction nodes once they're instantiated. And the only thing I've found regarding xpacket instructions is that they work as opening and closing tags of XMP metadata sections in media files.
We've found a couple of sites that have
xpacket
sections: talsunovads.lv and hlz.de.Checking the nodeType, it seems they are considered
nodeType
7. As we are not handling that use case, it returns an error:TypeError: Cannot read properties of undefined (reading 'length')
.We have to decide what to do with these nodes. Should we do the same as with CDATA nodes? It seems a similar case, as they are included inside the SVGs.
The text was updated successfully, but these errors were encountered: