Just an update on this. There’s been an update to the issue on the 10th of January with “Under Investigation. This issue is currently being investigated…”, which is a nice change from “more info needed”, or even worse “this isn’t a bug it’s a feature”, so they’ve managed to reproduce the bug and are looking into it.

This means if you see the 17.8.4 update available message, the fix isn’t in there, so don’t update yet. I’m using 17.8.0 - I’m not sure if the bug was introduced in 17.8.1, 17.8.2, or 17.8.3, but 17.8.0 is definitely safe to use.

Just an update on this. There’s been an update to the issue on the 10th of January with “Under Investigation. This issue is currently being investigated…”, which is a nice change from “more info needed”, or even worse “this isn’t a bug it’s a feature”, so they’ve managed to reproduce the bug and are looking into it.

This means if you see the 17.8.4 update available message, the fix isn’t in there, so don’t update yet. I’m using 17.8.0 - I’m not sure if the bug was introduced in 17.8.1, 17.8.2, or 17.8.3, but 17.8.0 is definitely safe to use.

Ah ok. Hopefully there’ll be another update soon then that might fix it (a programmer’s most feared words - “update available” ;-) ). Thanks! And also thanks for confirming not just dotnet.social that this is happenning on.

P.S. the bots which boost the content from here to Mastodon have also been broken for at least that long.

You know it was Christmas right?

I’m not sure what you mean about embedding a browser - do you mean writing your UI in XAML? If so I wrote a whole blog post suitable for beginners and up on how to write a MAUI UI using only C# Creating MAUI UI’s in C#

Well, that was interesting - when I cross-post a programming.dev post I originally made from Mastodon, it links to my Mastodon post instead of the !dotnetmaui@programming.dev post, which is here BTW

I found it. You just have to have the title on the first line, then mention the community, then your text :-)