On Sun, 2021-02-21 at 03:58 +0000, Wolfhart Totschnig
wolfhart(_dot_)totschnig(_at_)mail(_dot_)udp(_dot_)cl wrote:
To Liam's suggestions:
Are you producing XHTML with a DOCTYPE?
No, just HTML (see below).
rate, are the preambles of the XML files and of the stylesheet:
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="../zettel.xsl"?>
<zettel xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:noNamespaceSchemaLocation="../zettel.xsd">
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.1"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform";>
<xsl:output method="html" doctype-system="about:legacy-compat"/>
Does that help to identify a solution?
You could see if removing the schemaLocation made a difference,
although i doubt it. Unless you've installed an extension, Chrome
doesn't seem likely to have started doing XML Schema validation on
input to XSLT. And a system document type of about:legacy-compat is
correct and shouldn't cause problems.
Try opening the Network tab in the browser console and refreshing the
page and see what it's fetching.
Liam
--
Liam Quin, https://www.delightfulcomputing.com/
Available for XML/Document/Information Architecture/XSLT/
XSL/XQuery/Web/Text Processing/A11Y training, work & consulting.
Barefoot Web-slave, antique illustrations: http://www.fromoldbooks.org
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--