Currently we have to use non -native methods to enable popup closing by clicking outside. It would be interesting to have it natively.
I don't think so ,this is depend on business or user experience. Some where want to forcefully close the popup and somewhere outside click.Better to use own code for it.
Why not make this option available natively, allowing a simple true or false to define the behavior?If we apply this philosophy to other native platform components, they will become increasingly less functional and more complex to create and maintain.By providing these behaviors natively with easy configuration, we strengthen the low-code approach. This leads to less effort and greater impact.
Yes Now this make sense. This should be add in description so on it clear understanding.
Makes sense, with the property of simple true and false will not disrupt the default behaviour.If someone need to allow this simply can set the property to true or else default can be false for default closure.
This method is effective. A straight forward true/false option is enough to keep the default behavior unchanged. Users that wish to activate it may set it to true, whereas it can remain false for the normal behavior.
