Prochy

@cincuranet I would say that if the value is encapsulated between "," or ',' it should be never trimmed no matter what inside between them is. So also others whitespaces...

@torleifat get used to it...Don't expect a feedback any time soon from XAML team...From my experience they don't care too much to give any response. I'm at 1.5 and it...

After further research it looks like this is probably by standard Go behaviour (https://github.com/golang/go/issues/48723 )...So maybe would be fine to introduce keywords tcp4/tcp6 and if it's used, then it listen...

This trick works for me after upgrading 1.6 even though I decided to revert back to 1.5 because of other issues. ``` ExtendsContentIntoTitleBar = true; presenter.IsResizable = false; presenter.SetBorderAndTitleBar(true, false);...

Sorry guys, but can someone comment on this? This is absolutely terrible. There is obviously memory leak with using x:Bind for years and in the documentation there is no mention...

> @khoabui1412, in that repro it's not necessary to use a binding, you can just do `Click="click_event"`, but that's not to say that it should leak. But in the @akainth015...

The lack of communication drives me crazy and for me is something unacceptable. No idea if we can expect someone takes a look one day or not, why it is...