> 50 bubble charts produce corrupt chart SVG
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, node.js
- Domain
- backend, data-visualization
Research direction
Reproduce the export with not_working.json using the documented highcharts-export-server command, then compare its SVG with the working.json result. Trace the SVG export path responsible for bubble charts and verify that the output defines the xlink namespace and includes all 51 bubbles without corruption.
Written by the indexing model from the issue text.
Description
Expected behaviour
All 51 bubbles should be displayed without error.
Actual behaviour
The export server produces a corrupt SVG. When opening the file, following error is displayed:
error on line 44 at column 7087: Namespace prefix xlink for href on image is not defined
If I fix it by adding xmlns:xlink="http://www.w3.org/1999/xlink" to the svg tag, the image is displayed without an error. But no bubbles are shown.
Additional info
Base config structure used:
{
"chart": {
"type": "bubble",
"plotBorderWidth": 1,
"zooming": {
"type": "xy"
}
},
"title": {
"text": "Highcharts Bubbles Sizing"
},
"subtitle": {
"text": "Smallest and largest bubbles are equal, intermediate bubbles different."
},
"xAxis": {
"gridLineWidth": 1
},
"yAxis": {
"startOnTick": false,
"endOnTick": false
},
"series": [
{
"data": [
[
5,
5,
5
]
],
"sizeBy": "area",
"name": "Size by area"
},
]
}
Command used:
highcharts-export-server --logToFile false --allowCodeExecution -nologo true -type=svg -outfile /tmp/out.svg -infile /tmp/in.json --logLevel 4
Files used
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
naver/egjs-flicking#971 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
RADAR-base/radar-self-enrolment-ui#118 ·
Maintainers usually reply within 1 day
-
Renderer treats a sub-pixel width difference as a resize, which cancels the `motion()` entranceOpen
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
MicrosoftDocs/edge-developer#3970 ·
Maintainers usually reply within 1 day
-
agent/scanner hive/hosted-available-lke648397-260827-5n31 quality testing
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day