Min and Max mass listed don't take material into consideration

[KatieWoe]

Device
Samsung
OS
Win 11
Browser
Chrome
Problem Description
For phetsims/qa#1141
In studio, the mass ranges given for blocks may not take into account the material the block is currently made of. For example, the range for buoyancy.exploreScreen.view.blockAPanel.massNumberControl.massProperty is .1-27, but depending on the material is usually smaller than that.

Visuals

[KatieWoe]

Actually, this looks like it's already addressed in the examples doc, so it can probably be closed.

[Nancy-Salpepi]

I asked about this same thing in the Buoyancy slack channel!
Here is the response:

Sam Reid
My understanding is that the range shown there (at the bottom) is the total composite range for any material. It is static and unchanging, whereas the enabledRange is able to change. But studio (at the bottom) is supposed to show the static range, not the dynamic enabledRange.

Kathy Perkins
@arouinfar should weigh in on this question as well.

Amy Rouinfar

Yes, that behavior is fine. The examples clarifies that resultant volume needs to be 1-10L and recommends clients first refer to enabledRangeProperty before setting mass.

Nancy Salpepi

Wondering if that statement in the examples should come before the massProperty phetio IDs or do you think it is OK as is
@arouinfar?

[KatieWoe]

I noticed this discrepancy with the mystery fluids, which doesn't make sense to me.

[Nancy-Salpepi]

@KatieWoe your last comment is part of issue #405

[KatieWoe]

Ahh, thanks

[zepumph]

Ok great. Yes I believe all the actionables are in #405 and examples.md. Closing.

[zepumph]

Oh, we need to update examples. @arouinfar can you add this sentiment from the above comment:

Wondering if that statement in the examples should come before the massProperty phetio IDs or do you think it is OK as is
@arouinfar?