Dears,
It’s been a while I’ve been thinking about this. Given the use of a tb inside a GUI, I don’t see a good reason why the textBlock should by default act as a pointer blocker. Each time I use a container instead of a button, first thing I have to do is set the textBlock to “false”. I believe it would be more handy (and more logical) to have it the other way round, no?
Thanks and have a great day,
This would unfortunately be a breaking change 
cc @carolhmj
Hmmm yeah pointer blocker changes tend to cause a bit of confusion when they happen 
I’ll add @RaananW to ask what he thinks
yeah, that’s breaking back compat, but it makes sense…
in what scenario is it needed to be turned on? i mean, i wonder why it is on by default?
1 Like
Yes, that’s the question I also asked myself. But then, I can’t be sure of all use cases. However, using a textBlock to block pointer interactions seems a bit odd (in my opinion). Well, in any case, it’s not a big deal to declare it. I can still browse through all controls of this type and change it… but yes, I was just wondering… Thanks,