Is there a Blazor WebAssembly Firefox support issue for tracking? #82290
Description
Hello ... I'm addressing a tracking item for Blazor docs on this subject.
On May 11, 2022, I see ...
Thanks to a lot of work by @thaystg and help from others there is now firefox debugger support integrated into the debug proxy and tested as part of CI, any issues with that work can be opened as new issues. Closing this.
Cross-ref: #52698 (comment)
... but more recently on Oct. 28, 2022 ...
We still need to do some changes on blazor side to make it work, currently it's a little bit hard to use the firefox support on blazor, because Blazor only send the PDB's if it's Chrome or Edge. Maybe we should schedule a meeting if you want to implement the support, or you can wait, it's in my to do list do the changes on Blazor side.
Cross-ref: dotnet/AspNetCore.Docs#27411 (comment)
I don't see an issue on the repo that I can track on. Is there an issue? If not, I suppose that I might be able to check back periodically with an issue search for "Blazor WebAssembly Firefox"? Will that capture possible future work for my tracking? ... or did an offline meeting determine that for the foreseeable future that FF will not be supported? If FF support has been pushed off for consideration to .NET 9 or later, I'll close out my tracking item on it.