Yes, I added that property and the field look shrunk after that. I don't see any error in log and the field works fine. Just the look has changed.

I am using AEM 2022.11 cloud version. And I have just overlayed the page component dialog from v3 and added a field with numberField resourceType

Page property field having resource type: granite/ui/components/coral/foundation/form/numberfield shows issue in look, the moment I added msm-lockable property to it. The field shrinks, the increment/decrement toggle comes down the field and looks different. Is this a known issue?

I am using the latest cloud version of AEM which is 2022.11 and the above issue is a product bug.

On cancelling inheritance on Parent component, the child component within it also shows broken inheritance. I have the latest AEM Version. Is this an expected behavior?

A few things that were important:   we need to have cq-msm-lockable in all fields under page properties. This is always present for OOTB fields but should be added for the custom fields. If you are over-riding the existing tabs of the page properties, then make sure not the add the ootb fields again...

Inherit From Parent is already enabled

I have updated my pages through groovy and added property-values to get it in sync with the live copy. When I open a live copy page and open its page properties, I can see the connection with its language master. But I am not seeing the option of inheritance of the page properties. Refer image below...

How can i iterate through the values from page.getProperties() in groovy?

How can I update multi valued property using groovy, ex: cq:rolloutConfig is of String[] and i want to add values to this field using groovy.