User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; cs; rv:126.96.36.199) Gecko/20080311 Firefox/188.8.131.52 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; cs; rv:184.108.40.206) Gecko/20080311 Firefox/220.127.116.11 Would be great if Firefox provided URL parameters to XSLT transformer: http://example.com/data.xml?urlparam=value Especially useful in combination with document() XSLT function. --- data.xml: ---------- <?xml ... ?> <?xml-stylesheet type="text/xsl" href="example.xslt"?> --- example.xslt: ---------- <xsl:stylesheet version="1.0" ...> <xsl:param name="urlparam"/> ... <xsl:value-of select="$urlparam"/> This would echo "value". Reproducible: Always Steps to Reproduce: Construct some XLST formatted XML as described above and load the XML with a param in the URL. Actual Results: Firefox does not provide the param to the XLST processor. Expected Results: URL parameter provided to the XLST processor.
Component: General → XSLT
Product: Firefox → Core
QA Contact: general → xslt
Version: 3.6 Branch → Trunk
Hello, any considerations for this?
XSLT sees very little usage these days. Little enough that it's more valuable to invest in other parts of Gecko than XSLT. In fact, XSLT support is likely to eventually get removed. That's not going to happen very soon, and once it does happen there will be plenty of headsup. And it won't happen as long as XSLT continues to see a lot of usage, but that doesn't appear to be the case. https://www.chromestatus.com/metrics/feature/timeline/popularity/78 https://www.chromestatus.com/metrics/feature/timeline/popularity/79
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
I hope the XSLT functionality will NOT be removed.
XSLT is used quite a lot, especially in the enterprise applications. I personally know about 3 CRM/ERP systems using XSLT in browser, and quite some applications that export XML and use XSLT to preview these data outside of dynamic apps. Could you please share the source of your statistics of XSLT not being used?
You need to log in before you can comment on or make changes to this bug.