Remove feDropShadow from exported SVG files via config options?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, node.js
Research direction
Start by reviewing the Export Server v4 configuration and the path that produces exported SVG, comparing its output with v2.1.0 and the reported Jaspersoft/Batik failure. Done means determining whether a supported configuration prevents feDropShadow in the SVG and documenting the verified result.
Written by the indexing model from the issue text.
Description
Question
What options must be set in the configuration of the Export Server, so that the exported SVG does not include ?
How the problem came up
Export Server v2.1.0 does not included the <feDropShadow> in the SVG code.
Export Server v4 does however.
-> This crashes my Jaspersoft PDF-Report engine
Actual behaviour
Jaspersoft Reporting engine crashed when <feDropShadow> is in the SVG code.
+5.58 _ Exception: org.w3c.dom.DOMException: The current document is unable to create an element of the requested type (namespace: http://www.w3.org/2000/svg, name: feDropShadow).
+5.581 _ stack: [org.apache.batik.dom.AbstractNode.createDOMException(AbstractNode.java:408), org.apache.batik.anim.dom.SVGDOMImplementation.createElementNS(SVGDOMImplementation.java:201), org.apache.batik.anim.dom.SVGOMDocument.createElementNS(SVGOMDocument.java:374), org.apache.batik.dom.util.SAXDocumentFactory.startElement(SAXDocumentFactory.java:651), com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:509), com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:374), com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2783), com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:601), com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:112), com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:504), com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:841), com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:770), com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141), com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213), com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:642), org.apache.batik.dom.util.SAXDocumentFactory.createDocument(SAXDocumentFactory.java:453), org.apache.batik.dom.util.SAXDocumentFactory.createDocument(SAXDocumentFactory.java:357), org.apache.batik.anim.dom.SAXSVGDocumentFactory.createDocument(SAXSVGDocumentFactory.java:225), org.apache.batik.anim.dom.SAXSVGDocumentFactory.createSVGDocument(SAXSVGDocumentFactory.java:135), net.sf.jasperreports.renderers.util.SvgDataSniffer.getSvgInfo(SvgDataSniffer.java:87), net.sf.jasperreports.renderers.util.RendererUtil.getSvgInfo(RendererUtil.java:126), net.sf.jasperreports.renderers.util.RendererUtil.isSvgData(RendererUtil.java:107), net.sf.jasperreports.renderers.util.RendererUtil.isSvgData(RendererUtil.java:146), net.sf.jasperreports.engine.export.JRPdfExporter$InternalImageProcessor.process(JRPdfExporter.java:1592), net.sf.jasperreports.engine.export.JRPdfExporter$InternalImageProcessor.access$300(JRPdfExporter.java:1547), net.sf.jasperreports.engine.export.JRPdfExporter.exportImage(JRPdfExporter.java:1487), net.sf.jasperreports.engine.export.JRPdfExporter.exportElements(JRPdfExporter.java:1105), net.sf.jasperreports.engine.export.JRPdfExporter.exportPage(JRPdfExporter.java:1068), net.sf.jasperreports.engine.export.JRPdfExporter.exportReportToStream(JRPdfExporter.java:932), net.sf.jasperreports.engine.export.JRPdfExporter.exportReport(JRPdfExporter.java:552), net.sf.dynamicreports.jasper.builder.JasperReportBuilder.export(JasperReportBuilder.java:600), net.sf.dynamicreports.jasper.builder.JasperReportBuilder.toPdf(JasperReportBuilder.java:536), dynamicreports.Rep3.exportReportFile(Rep3.java:5449), dynamicreports.Rep3.makeReport(Rep3.java:5078), dynamicreports.Rep3.main(Rep3.java:6112)]
- Dominant language
- JavaScript
- Stars
- 368
- Forks
- 265
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from highcharts/node-export-server
-
Update Puppeteer to version 25.11.0+ to allow ARM64 linux images to run node-export-serverPossibly taken @daniatic claimed this 3 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
highcharts/node-export-server#686 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
highcharts/node-export-server#680 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
highcharts/node-export-server#679 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
highcharts/node-export-server#678 ·
-
Not working on s390xOpen
Difficulty 4/5 3-5 days Newbie friendliness 30/100
highcharts/node-export-server#676 ·
All issues in highcharts/node-export-server
Similar issues
-
ci-install-db-tools stall-case tests flake: stalled apt-get can be killed before it logs its callOpeneffort:low model:light plan planner:opus-5-5 tests
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Bug 🐞
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mozilla-mobile/firefox-ios#35986 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
component:sight
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agentic-os-org/ANOLISA#6738 · 2 comments ·
Maintainers usually reply within 1 day
-
bug Durable Agents Observability (AI Telemetry) status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
mastra-ai/mastra#26470 · 1 comment ·
Maintainers usually reply within 1 day