Suppress ERR_BLOCKED_BY_ORB noise from third-party ad creatives

[JakubMrozek]

Summary

• Suppress ERR_BLOCKED_BY_ORB errors in onConsoleMessage and onReceivedError WebView callbacks
• These errors are triggered by cross-origin resource requests from third-party ad creatives that lack proper CORS headers — not actionable on our side
• Reduces noise in logs and Sentry

Fixes KON-1264

🤖 Generated with Claude Code

[JakubMrozek]

@claude

[claude]

Claude finished @JakubMrozek's task in 53s —— View job

---

Code Review

• Read changed files
• Analyze the changes
• Post review feedback

---

The change is clean and well-targeted. A few observations:

What the final diff actually does

Only onReceivedError is modified — the onConsoleMessage filter was added in the first commit then removed in the second (87464de). This is the right call: ERR_BLOCKED_BY_ORB is a network-level error reported by the Chromium stack, not a JS console message, so filtering it in onConsoleMessage would have been incorrect.

Minor note: the PR description still mentions suppressing in both callbacks, but the final code only touches onReceivedError. Worth updating the description for accuracy.

Consistency with existing patterns

The approach mirrors the existing favicon.ico suppression in onReceivedHttpError (lib/src/widgets/kontext_webview.dart:207), which is a good precedent to follow.

Platform scope

ERR_BLOCKED_BY_ORB is Chromium-specific (Android). On iOS (WKWebView), ORB blocking surfaces differently or not at all through this callback, so the filter is a no-op there — that's fine.

String matching

error.description.contains('ERR_BLOCKED_BY_ORB') is pragmatic. An exact equality check (==) would be slightly more precise, but given this is a well-known, stable Chromium error string, contains is fine and more resilient to any prefix/suffix variation.

Overall: LGTM. The change is minimal, well-commented, and correctly scoped.