[dialog] unable to reference dialog node #1266
Replies: 2 comments
-
All 'node/element getters' are private (or actually protected to be really precise), so they are only accessible for Subclassers. For some of them it might make sense to make them public (we could add an extra getter that calls the extisting one) but I would like to keep this limited. @LarsDenBakker is there a reason you need it for this particular getter? (It's the element you provide via content projection I think, right?) |
Beta Was this translation helpful? Give feedback.
-
I think this is a good enhancement but I agree with Thijs that we have to factor in pros and cons, the cons being exposing this API makes us less flexible. For us to pick this up we definitely will need to hear about use cases where you really need to grab the _overlayContentNode as a public property. Will move this to discussions |
Beta Was this translation helpful? Give feedback.
-
The dialog element has no public API to get a reference to the content node. There is a
_overlayContentNode
property but it is private.Beta Was this translation helpful? Give feedback.
All reactions