We contacted several websites. Some confirmed they will be positively >> impacted. >> > Microsoft Teams, the #1 requested adding >> "allow-top-navigation-to-custom-scheme" to opt-out from this feature >> individually. >> > > It's reassuring to hear they'd be willing to use an opt-out. > Have you reached out to others on that list? It seems like tackling the > top ~3 would significantly reduce the risk. >
I confirm I sent an email for every website we see: the top 8 on Windows and a few others on Android. I asked them to confirm reception. > > Please make sure you use CountDeprecation > <https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/platform/instrumentation/use_counter.h;l=45?q=Deprecation%20UseCounter&ss=chromium>, > > to get deprecation reports sent automatically. (unless there are particular > technical reasons that make this more complex than it should be. If that's > the case, let's discuss more) > This can't only be used in blink unfortunately. This is about navigation, and happens when we are out of handlers, before calling external applications. I can't make use of CountDeprecation here. It is not impossible to create new IPCs and get it plumbed to the renderer process, but that's probably more complex than what it deserves. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/bcce7cbf-b5de-411f-90ef-ec2d5a7e717an%40chromium.org.
