Fix Images Page on Mobile Version of Google #485
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
iorate
approved these changes
Jun 6, 2024
|
🎉 This PR is included in version 8.7.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes #476, improving support for blocking images on the mobile version of Google search.
Demo
google-mobile-udm2.webm
Additional Comments
Currently, it seems that the mobile version of Google search mostly uses
udm=2, instead oftbm=isch.I tested on multiple devices, VPNs, and regions, and I was not able to get a
tbm=ischon mobile.I'm not sure why that's the case, but things are now working with the new
serpHandler.