FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Website search unexpectedly redirects to Google · Issue #721 · processing/processing-website · GitHub

Repository navigation

Website search unexpectedly redirects to Google #721

Open

Description

Select the most appropriate label(s) for this issue.

No response

Describe the bug

When using the search bar on processing.org, entering a query such as “typography” redirects the browser to a Google search for typography site:processing.org.

Steps to reproduce

  1. Visit processing.org.
  2. Open the site search.
  3. Enter a search term, for example “typography”.
  4. Submit the search.
  5. The browser leaves processing.org and opens a Google search results page.

Current behavior
Searching from the Processing website navigates the user away from processing.org to Google.

Expected behavior

Search results are displayed within the Processing website, or the UI makes it clear beforehand that search will open an external Google search.

Screenshots

Browser

Chrome

Browser version

154.0.8037.58 (Official Build) (64-bit) (cohort: Stable)

Operating system

Windows

Smartphone details

No response

Additional context

This appears to affect the site-wide search rather than a specific documentation page. I reproduced it while searching for “typography”.
The search field visually appears to be part of processing.org, so the navigation to an external Google results page was unexpected.
I would also be interested in working on a fix if the maintainers consider this behavior unintended.

Activity

  1. SableRaf commented on Sep 30, 2026

    Collaborator

    Hi @A5hank and thanks for flagging this.

    This is the intended behavior. I believe this was a compromise made during the creation of the website because of the complexity of building a custom search feature. I agree that it is not ideal. At the same time, I would personally rather avoid displaying a Google logo or the Google name so prominently the website.

    A potential quick fix could be to switch to Ecosia which seems to do a decent job surfacing relevant documentation for Processing. I'm using your "typography" example here (see screenshot below), but I tried a couple other keywords too and the results were good too.

    In that case, we could then write "Search with Ecosia" instead of "Search".

    Is that something you'd like to contribute a Pull Request for?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions


      Back | FazBrowse Home | New Git URL