Bug reportNov 11, 2026· 0:35· 12 views
Victory VictoryBar: animation onExit.before produces 'undefined' in SVG path d attribute
0:35 total
Comments · 0
Be the first to comment.
Bug reportby SceneRecap AI
mediumVictoryBar bar path generation during animated exit transitions (animate.onExit.before). A y-related value appears to resolve to undefined when the path d string is built.
os: macOSdpr: 1url: /open-source/victory/docs/guides/animationslocale: en-USbrowser: Chromium 151.0.7922.34timezone: Europe/Berlinviewport: 1280x720
Repro steps
- 1.Open the Victory docs page /open-source/victory/docs/guides/animations.
- 2.Confirm the page title is 'Animations | Victory'.
- 3.Scroll down about 600px to the Transitions section.
- 4.Wait for the Transitions LIVE VIEW to load and run its exit transition. Watch the browser console.
Expected
The Transitions example animates entering and exiting nodes using the onEnter and onExit before/after functions. Every SVG path d attribute gets a numeric value, and no console errors are logged.
Actual
Right after the Transitions LIVE VIEW loads, the console logs three errors of the form '<path> attribute d: Expected number' where the path value contains 'undefined' (for example "M 364, undefined \nA 0 0…"). At 31.0s an on-screen banner reports that SVG parse errors are emitted to the console on each exit cycle.
Evidence
visualControl: the first example (scatter chart LIVE VIEW) renders points and axes at the top of the page. No console errors are logged before the Transitions section loads.
visualThe Transitions section is visible. A second LIVE VIEW below it starts loading and shows red bars.
consoleError: <path> attribute d: Expected number, "…00000000000006, undefined \nA 0 0…".
consoleError: <path> attribute d: Expected number, "M 364, undefined \nA 0 0…".
consoleError: <path> attribute d: Expected number, "…99999999999994, undefined \nA 0 0…".
visualPage stays on the Transitions section with no further interaction logged.
visualA red banner reads 'SVG parse errors emitted to console on each exit cycle (see Console)'.
Issue markdown (copy-paste ready)
## Summary On the Victory Animations guide, the Transitions example logs SVG `<path>` `d` attribute errors. The path strings contain `undefined` where a number is expected. This matches the onExit.before behavior described in the report title. ## Environment - Browser: Chromium 151.0.7922.34 - OS: macOS - Viewport: 1280x720, DPR 1 - Locale/Timezone: en-US / Europe/Berlin - URL: /open-source/victory/docs/guides/animations ## Steps to reproduce 1. Open `/open-source/victory/docs/guides/animations` (0.0s). 2. Scroll down about 600px to the **Transitions** section (2.6s). 3. Let the Transitions LIVE VIEW load and run. Watch the console (3.8s). ## Expected Entering and exiting bars animate using the onEnter/onExit before/after functions. Every path `d` value is numeric, and the console shows no errors. ## Actual The console logs three errors between 3.8s and 3.9s: - `Error: <path> attribute d: Expected number, "…00000000000006, undefined \nA 0 0…".` (3.771s) - `Error: <path> attribute d: Expected number, "M 364, undefined \nA 0 0…".` (3.818s) - `Error: <path> attribute d: Expected number, "…99999999999994, undefined \nA 0 0…".` (3.878s) At 31.0s a banner reads: "SVG parse errors emitted to console on each exit cycle (see Console)". ## Control The first example on the page, the scatter chart at 0.0s, renders without logged errors before the Transitions example loads. ## Suspected area VictoryBar path generation during exit transitions (`animate.onExit.before`). A y coordinate looks like it resolves to `undefined` when the bar path is built. *Recorded with SceneRecap.*
Your recordings could explain themselves too.
Free plan · silent recordings welcome · bug reports included.
Try SceneRecap free →