Bug 223253

Summary: Cannot click on DuckDuckGo search results, requires macOS user agent quirk
Product: WebKit Reporter: Michael Catanzaro <mcatanzaro>
Component: WebCore Misc.Assignee: Michael Catanzaro <mcatanzaro>
Status: RESOLVED FIXED    
Severity: Normal CC: bugs-noreply, cgarcia, konrad, mcatanzaro
Priority: P2    
Version: WebKit Nightly Build   
Hardware: PC   
OS: Linux   
Attachments:
Description Flags
Patch mcatanzaro: commit-queue-

Description Michael Catanzaro 2021-03-16 07:25:55 PDT
It seems DuckDuckGo changed something on their end, because clicking links on search results no longer works. It doesn't appear to be due to any WebKit or Epiphany change.

Possibly related to one of these web inspector errors:

[Error] Unrecognized Content-Security-Policy directive 'manifest-src'.

[Error] Unrecognized Content-Security-Policy directive 'worker-src'.

[Error] Unrecognized Content-Security-Policy directive 'manifest-src'.

[Error] Unrecognized Content-Security-Policy directive 'worker-src'.

There is also another web inspector error:

[Error] Refused to execute https://duckduckgo.com/post.js as script because "X-Content-Type-Options: nosniff" was given and its Content-Type is not a script MIME type.

But that one is not related because it appears in the Firefox console too, and DuckDuckGo still works in Firefox.
Comment 1 Michael Catanzaro 2021-03-16 09:42:07 PDT
Adrian observes: """go to web inspector → pick <a> element → go to “Node” tab → ”Event Listeners” → “click” → uncheck the “Enabled” toggle → tada! link works"""

cb = cd.handle = function(ck) {
                    return typeof bJ !== aB && (!ck || bJ.event.triggered !== ck.type) ? bJ.event.dispatch.apply(cb.elem, arguments) : aF
                };
Comment 2 Michael Catanzaro 2021-03-16 12:18:51 PDT
Phil and Alex say Safari is not affected -- we're not sure why -- so it's gonna be hard to get DuckDuckGo's attention on this.
Comment 3 Michael Catanzaro 2021-03-16 12:47:27 PDT
It works if we use a macOS user agent quirk. <_<
Comment 4 Michael Catanzaro 2021-03-16 13:04:04 PDT
Created attachment 423387 [details]
Patch
Comment 5 Michael Catanzaro 2021-03-16 13:10:05 PDT
(In reply to Michael Catanzaro from comment #0)
> Possibly related to one of these web inspector errors:
> 
> [Error] Unrecognized Content-Security-Policy directive 'manifest-src'.
> 
> [Error] Unrecognized Content-Security-Policy directive 'worker-src'.
> 
> [Error] Unrecognized Content-Security-Policy directive 'manifest-src'.
> 
> [Error] Unrecognized Content-Security-Policy directive 'worker-src'.

These errors are unrelated.
Comment 6 Konrad Dzwinel 2021-03-16 14:21:47 PDT
>  it's gonna be hard to get DuckDuckGo's attention on this.

Hey folks, sorry for trouble, we just reverted the changed that broke this.
Comment 7 Michael Catanzaro 2021-03-16 15:16:06 PDT
Thanks Konrad. Not sure how you noticed even *before* we reached out, but that's pretty excellent, thanks!
Comment 8 Carlos Garcia Campos 2021-03-17 02:12:59 PDT
(In reply to Konrad Dzwinel from comment #6)
> >  it's gonna be hard to get DuckDuckGo's attention on this.
> 
> Hey folks, sorry for trouble, we just reverted the changed that broke this.

Thanks! It would be sad if we have to use a user agent quirk for ddg.
Comment 9 Konrad Dzwinel 2021-03-17 05:12:58 PDT
> It would be sad if we have to use a user agent quirk for ddg

Agreed, please ping us if it will ever become an issue in the future.


> Not sure how you noticed even *before* we reached out

Through the magic of RSS ;) We are monitoring bugzilla for bugs mentioning "DuckDuckGo".