while writing bar/barh tests for bug #65671, i came upon a few cases where changes to bar data do not trigger needed updates to axes properties:

1) changing to horizontal results in incorrect yaxis ticks/labels
h = bar (2:4);
set (h, 'horizontal', 'on');

result should be identical, or close too h = barh(2:4).  vertical axis ticks/labels are not updated however, leaving a number of intermediate values.  see attached figure comparing both for octave 9.1.0 and matlab. (results are independent of the pending patch for bug #65671)

2) changing xdata moves the bars but fails to update xlim and xticks to match:

hf = figure(); hax = axes('parent',hf);
h = bar (hax, 2:4);
set (h, 'xdata', [3:5]')  # stored vert, but horiz no difference
set (hax, 'xlim', [2.5 5.5]);

as shown in the figure next to a matlab comparison, setting xdata fails to update xlim to show the bars, and even with a manual xlim the new xaxis ticks/lables have not been created.

since changing xdata calls h= bar () again, not sure why the axis setting isn't occurring along with it.

will be writing up xtest BISTs to capture these along with tests for bug #65671. then will give these a look after that one's finished.