Change on stack does not update the chart properly with non-default scaleId

[TheoLaperrouse]

Expected Behavior

When I change the stack of one of the datasets, I would like the graph to update correctly.

Current Behavior

Here, the dataset stays in the same place when it should go down

Steps to Reproduce

Example

Here is a link with small datasets where you can see the issue : JsFiddle

Here is what I would like to have when I update the chart : JsFiddle

Chart Config:

const myChart = new Chart(ctx, {
  type: "bar",
  data: {
    labels: ["January", "February", "March", "April", "May", "June"],
    datasets: [
      {
        backgroundColor: "rgba(255,99,132,0.8)",
        label: "Dataset 1",
        data: [12, 19, 3, 5, 2, 3],
        stack: "0"
      },
      {
        backgroundColor: "rgba(54,162,235,0.8)",
        label: "Dataset 2",
        data: [13, 19, 3, 5, 8, 3],
        stack: "0" //When I change this, the chart is not updated correctly
      },
      {
        backgroundColor: "rgba(75,192,192,0.8)",
        label: "Dataset 3",
        data: [13, 19, 3, 5, 8, 3],
        stack: "0"
      }
    ]
  },
  options: {
    scales: {
      yAxes: [
        {
          ticks: {
            beginAtZero: true
          }
        }
      ]
    }
  }
});

Context

When I edit a chart, the editing preview is not the same depending on whether I reload the page or not.

Here is when i'm editing:

Then i save the configuration and i update the chart:

Environment

• Chart.js version: 3.2.0
• Browser name and version: Firefox 88.0.1 (64 bits)

[kurkle]

Reproduces with master: https://jsfiddle.net/f1mt0hg5/1/

[kurkle]

The issue is invalid scales config, works fine if the scales are configured properly (master): https://jsfiddle.net/f1mt0hg5/3/
3.2.1 still has the issue: https://jsfiddle.net/m8ex0sbw/

[kurkle]

I think this was fixed in #9105

[TheoLaperrouse]

Hello again,
We have upgraded our application to chartJS 3.3.0 and we are still experiencing the same problem. After spending quite a bit of time looking at our chart configurations, it seems that the problem is that we are using yAxisID to reference the y-axis in our datasets.

When we use y-axis-1 as the axis name and reference it in our datasets. We have the same problem as mentioned above in the issue.
https://jsfiddle.net/guza6sec/1

However, when we remove these yAxisIDs and change the name of the y-axis to y, the behaviour is what we want.
https://jsfiddle.net/guza6sec

For us, however, these two examples should have the same behaviour.

[kurkle]

@TheoLaperrouse looks like there is another bug in there.

[etimberg]

I believe the 2nd issue was fixed in #9170

[kurkle]

Looks like I had linked a wrong number there, this was indeed fixed.