I don't think you want to rename attributes that way, as#18592 is going to do the opposite.

I did the renames because the 3D collections were inconsistent between each other. I pushed to plural to match the 2D version, will push them the other way.

Because we have a shortage of people to review mplot3D, this being a critical bug, and in the interest of getting 3.3.3 out@QuLogic can merge this at his discretion on a single review.

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

$ git checkout v3.3.x$ git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

$ git cherry-pick -m1 fa547835c7ea262b706f8bdde5bb7433ccef4f79

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

$ git commit -am 'Backport PR #18929: FIX: make sure scalarmappable updates are handled correctly in 3D'

4. Push to a named branch :

git push YOURFORK v3.3.x:auto-backport-of-pr-18929-on-v3.3.x

5. Create a PR against branch v3.3.x, I would have named this PR:

"Backport PR#18929 on branch v3.3.x"

And apply the correct labels and milestones.

Congratulation you did some good work ! Hopefully your backport PR will be tested by the continuous integration and merged soon!

If these instruction are inaccurate, feel free tosuggest an improvement.