Skip to main content

Hi !


A question targeted to the dev team here,

I’ve just noticed that within an instance of a component, the absoluteRenderBounds

properties of a text node isn’t populated. It seems that it is only populated “if” the text of the instance has been modified (compared to the original instance)


I understand the logic behind, but I still wanted to point that out to check if it’s the intended behaviour or a bug,


And if it is intended, i also would like to know if there are others properties like that to watch out for.


For example, i tried to add an effect on the text in the original component, to test wether the same logic applied, aka wether the effects properties of that text within instances wouldn’t be populated but it is there in that case, which makes me tend to think that the behaviour of absoluteRenderBounds might be unintended.


Thanks in advance for your inputs,

and thanks for the awesome API / environment, it’s a pleasure to work with it !

Ok, it’s not at all what i thought, sorry


what causes the absoluteRenderBounds to be null is because the text was outside of the visible area inside a clipped container, so i guess it makes total sense, since it’s not actually rendered.


In my use case (developing a code export plugin), it would still be convenient if you did populate that field (with the value where they should appear if it was visible) since some designers might lay some things outside of the visible portion on the page, (ex : article outside of the scroll area), and i still want to be able to treat those elements optimally. But i would understand if that’s not a priority.

Terms & ConditionsCookie settings