-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Looking to report a bug to the MSEdge mobile team #154
Comments
Thanks for reaching out.
I hope this helps. |
That's helpful to some extent, though I assume they'd want more details, which I voluntarily didn't provide here because indeed this isn't the right place for this conversation. The ideal solution would be to have them open a proper reporting channel somewhere.
If it is expected of me a website operator to go through the following to report a technical bug in a browser I do not use:
All other browser vendors (both major and minor ones) have proper reporting channels for all their platforms. If Microsoft doesn't believe that to be worth their time, then reporting it rather than just blocking the faulty browser also isn't worth mine. And I can very much empathise with the timesink that triaging incurs, as we operate a pretty large web platform and thus have to deal with our own stream of bug reports of varying quality. All in all, thanks for the quick response, even if the outcome isn't particularly encouraging. edit: Note that while my tone is probably a bit over the top, I appreciate that it is not your fault in any way, and I appreciate you taking the time to answer nonetheless. |
Hello,
I'm looking for a contact to report a bug to the Edge mobile apps team, from the website operator side (NOT the application/user side), with how Edge Mobile 113 on iPadOS 16.3 behaves (that guy:
Mozilla/5.0 (iPad; CPU OS 16_3 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) EdgiOS/113.0.1774.36 Version/16.0 Mobile/15E148 Safari/604.1
).Tis about broken caching, very similar to mozilla-mobile/firefox-ios#12113 by the looks of it.
Despite looking around, I cannot find any indication of how/where to report this kind of issue, so I'm hoping someone on the DevTools team may know. Otherwise our only option is to straight up block the browser by UA and encourage end-users to report the issue themselves (since end-user bug report seems to be the only available channel), and I'd rather not resort to that kind of method.
Thanks
The text was updated successfully, but these errors were encountered: