I'm not completely sure if this is more like a bug or a potential minor improvement. I'm sorry if this turns out inappropriate to be put under "bug".
For a 2d histogram (TH2), FitSlicesX() uses the x axis range set by the user (because it calls Projection) but ignores the y axis range set by the user. An intuitive example is shown in test2d.cpp.
For a 3d histogram (TH3), FitSlicesZ() ignores all the axis ranges set by the user. An example is attached as test3d.cpp.
This kind of bothers me because Projection, Profile and many other histogram methods all honor the axis range set by the user and I find this really convenient. Is it possible to make FitSlices behave the same?