Could we remove Average Reading Rate and rely on MIN + MAX / 2 to determine a central point? In this case, it would become 183 instead of 189.

Alternatively, we could leave AVERAGE_READING_RATE, but have it be a customizable input so you can set this value. Then, display as range subtracts/adds 50 to whatever value you set.

I think it makes more sense to have AVERAGE_READING_RATE be the constant and the range be a static +/- value

I left an in-depth comment about the direction I think we should go on #53776 (comment)

Now I understand what this effect wants to do.

So you want to enable displayAsRange only in newly inserted blocks? Do we need to enable displayAsRange by default?

So you want to enable displayAsRange only in newly inserted blocks?

Yes, because there will already be instances of this block in the wild that we don't want to change.

Do we need to enable displayAsRange by default?
This would change all the blocks already out there...

Is it possible to set displayAsRange to false in the newly inserted block as well? Do you think this is a problem from an A11y perspective?

Once the block is inserted you can still turn the range off. I think this presents a good compromise - it encourages people to use the more accessible version but doesn't force it for those who really want to use the simpler version.

I see, then, how about this approach:

• Define displayAsRange as true by default in block.json
• Update displayAsRange to false if the blockWasJustInserted is false

Because I think the default values ​​in block.json should represent the actual behavior of the most recent block.

I tried this originally. The problem with this is the frontend rendering - if blocks aren't updated in the editor then they won't have displayAsRange as false so they will get converted to the new range format.

Thanks for the detailed explanation. I understand your approach is the best.

I wonder if this could have been done as part of the block deprecation migrate method for old blocks.

Current logic seems inconsistent, IMO. Newly inserted blocks will have different defaults, while block.json spec declares a different one.

I looked at doing this with a migration. The problem is that default attributes are not set, so a newly inserted block with displayAsRange: true won't have any attribute set, which makes it indistinguishable from an old block which just doesn't have the attribute yet.

If you can find a way then i'm very open to it :)