Look-ups always have "Sorry no definition found"

[Shahius]

I noticed today. Look-ups always have "Sorry no definition found"
Firefox Nightly 136.0a1 (2025-01-10) (64-bit).

[lqdm12]

it's happening here too!

134.0.1 (64-bit) Linux Unbuntu

[siddharthbandhu]

Having the same issue.

Firefox 134.0.1 (64-bit) on Windows 11.

[5rxiq]

133.0.3 (64-bit) on MacOS

[roman-aleksejuk-telia]

Same thing, Windows 11, Firefox 128.6.0esr

[harshsingh0930]

Firefox version 134.0.1, same thing

[ChauvinistCook]

Same here.
Firefox 134.0-1

[vayulove]

Same problem here. (Firefox on Linux, 133.0.3 (64-bit)) I can imagine that it's hard to keep up with problems. Do you have any idea of if, and if so, when, it might get fixed? This is one of my very favorite extensions. I'm constantly looking up definitions.

[lqdm12]

same to me @vayulove! I'm constantly looking up definitions :/

[rcostanza]

Inspecting the extension on Firefox, the issue is that Google now responds the search request with a redirect page instead of the results.

"Please click here if you are not redirected within a few seconds."

[pnbabu]

Same issue here. Firefox 134.0.1 (64-bit) on macOS.

[OzMerry]

Same here. Windows 11 24H2, Firefox 64-bit 134.0.2.

[graterol-oswaldo]

Same here. Firefox 134.0.2 (64-bit), Debian GNU/Linux 12 (bookworm)

[graterol-oswaldo]

I checked the extension, and tried to search for the meaning some words.

While inspecting using the "web developer tools", I noted the extension made a request with the following format:

"https://www.google.com/search?hl=en&q=define+leather&gl=US".

If I perform that request from a web browser URL, in the chain of requests that are made, the first request to that URL returns an output like:

and then, all other requests proceed until the expected result is finally shown.

However, the extension internally, despite receiving a response code 200, had the following response body:

The extension's source code is trying to get a querySeletector output of a document from the first request, but the document does not contain the expected data yet.

I hope you find this information useful.

Thanks.

[curable-online]

Same here, Firefox 133 and 134, Arch Linux.

[trophalt]

having same issue version 133, updated to version 134.0.2 (64 bit) still having same problem, using macbook pro