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.
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 };
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.
It works if we use a macOS user agent quirk. <_<
Created attachment 423387 [details] Patch
(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.
> 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 Konrad. Not sure how you noticed even *before* we reached out, but that's pretty excellent, thanks!
(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.
> 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".