@noelle sometimes girls do also
@aescling i would not be remotely surprised if this bug was also in Chrome but i don’t have it installed to check
it’s not whether it is the first non‐default namespace; in fact it is just that some namespaces must be declared before others (by some unknown‐to‐me standard) or else the whole fuckin’ thing breaks.
the XSLT will correctly process if you simply change the order of the namespace declarations on the root element, which is not something which should ever determine whether an XML document is able to be processed or not
Safari consistently fails to process XSLT when it includes an XPath with a namespace which is the first non‐default namespace declared in the root element, but only sometimes
the name or value of the namespace does not appear to matter; however, and for reasons i cannot seem to determine but presumably has to do with document structure somehow, it only manifests for certain namespaces which have only been used in the document in certain (specifics unknown) ways
@Satsuma also, same hat
@Satsuma a comfy person
@Satsuma pyjamas are almost a costume
@Satsuma did you dress up in costume
Administrator / Public Relations for GlitchCat. Not actually glitchy, nor a cat. I wrote the rules for this instance.
“Constitutionally incapable of not going hard” — @aescling
“Fedi Cassandra” – @Satsuma
I HAVE EXPERIENCE IN THINGS. YOU CAN JUST @ ME.
I work for a library but I post about Zelda fanfiction.
For the time being, this is mostly a mirror of <https://status.ladys.computer/>. Want to get in touch? E·mail me!