You get the value properly displayed when loading the page, before you touch the input? On your screenshot you’ve clicked the input. Just to make sure…
@johan On a side note: It would help if you always copy the full field definition, not only parts of it. Then we can copy and paste it into our reference projects in the same way you have it in your blueprint.
Yes that solves it with the tooltip. But I only allow one row. When adding the opacity to the default, it creates two rows when creating a new page. How do you add default values to the same row?
As a side note, after some thoughts. It should also work having the default value inside the corresponding field, in this case as in my first code, inside the opacity field. And not to the structure field. Currently I’m adding the opacity as a default attached to the structure field, but it’s just a hack to have the tooltip display the value when first viewed.
In my case the opacity field is just shown when another field is selected. Hence, the value isn’t needed every time. Having the default value attached to the structure field, there will always be a default value in the content file.
opacity: “0.2”
Even though it’s not used.
If the default is attached to the opacity field instead, when that field is not used and the row is saved the value in the content file will be blank: