You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug] pptx: axismin/axismax/axisnumfmt on an /axis[@role=value2] path change the primary value axis #503
The axis path's own names work as expected: --prop min=-30 --prop max=12 --prop 'format=0.0"%"' on the same path sets the value2 axis. axistitle on the same path also reaches the value2 axis.
Expected: on an /axis[@role=...] path, axismin, axismax and axisnumfmt (and its axisnumberformat alias) apply to the axis the path addresses, like min, max and format. If they aren't supported on an axis path, an UNSUPPORTED props warning instead of a silent change to another axis.
Notes
The chart help describes these props as shortcuts for /chart[N]/axis[@role=...] min, max and format, so it's natural to use them on an axis path. On a dual-axis chart, the result rescales the bars to the line's units and gives them the line's format, which breaks the chart.
Our workaround: on an axis path, we rename axismin, axismax and axisnumfmt to min, max and format before sending the command.
I'd like to work on this. I reproduced it on main (fb98e59) exactly as described — the set reports success on the role=value2 path while the bounds and format land on the primary value axis — and I have a fix with the arm matrix measured. PR coming shortly.
Two things the repro confirmed beyond the report, for whoever reviews it:
axisnumberformat (the other declared alias of axisnumfmt) has the same defect, so both spellings need the branch.
The aliases also mis-target on the category path: --prop axismin=… --prop axismax=… --prop axisnumfmt=… on /axis[@role=category] writes the primary value axis, while the same path's own names min/max/format write the category axis.
Activity
argszero commentedon Oct 14, 2026
I'd like to work on this. I reproduced it on
main(fb98e59) exactly as described — thesetreports success on therole=value2path while the bounds and format land on the primary value axis — and I have a fix with the arm matrix measured. PR coming shortly.Two things the repro confirmed beyond the report, for whoever reviews it:
axisnumberformat(the other declared alias ofaxisnumfmt) has the same defect, so both spellings need the branch.categorypath:--prop axismin=… --prop axismax=… --prop axisnumfmt=…on/axis[@role=category]writes the primary value axis, while the same path's own namesmin/max/formatwrite the category axis.