We should try to guarentee that any element in the base element should be accessible when the bindings in the super element get instantiated. Failing to do it might cause to an attempt to access uninitialized sub-object at that point. Several bugs related to this has been reported so far but resolved in "hacky" way. (i.e https://bugreports.qt.io/browse/QTBUG-107795, https://bugreports.qt.io/browse/QTBUG-107900)
Let's eventually come up with a proper fix on this issue.
|For Gerrit Dashboard: QTBUG-108102|
|433459,8||QmlObjectCreator: play nice with grouped properties||dev||qt/qtdeclarative||Status: MERGED||+2||0|
|449060,2||QmlObjectCreator: play nice with grouped properties||6.5||qt/qtdeclarative||Status: MERGED||+2||0|