Rick Strahl

For me it fails in FireFox too: 

Great! That worked perfectly. So that solves the immediate problem I have here, but the question in the issue is still at point for whether there could be better support...

Here's some more info on this particular issue: It appears the problem occurs if the window stack is different when the global handler is detached than when it was attached...

Thanks will take a look next time I take a look at this. The UI is pretty old and of course predates .NET Core and Linux requirements so at the...

There's nothing built-in to support multi-tenant directly and that's because we basically hook into the .NET native localization pipeline which has no concept or support for extensibility. If you search...

Closing because while I agree it would be useful for some scenarios this is too app specific to provide natively. May rethink this in the future but it will require...

Sorry I don't know much about custom culture handling in different environments. Maybe somebody else can help out here?

True - is that really something you need to do though? Easy enough to add but takes up UI space.

To add we need to add a custom UI form or something that lets you specify the language to remove.

Those are invalid resource IDs in various environments (WebForms in particular). This may not matter to you. I guess we can get rid of that since WebForms is obviously fading...