Page Find and Web Inspector search are different tools

01Choose the thing you want to find

Safari documents ordinary page search and navigation. WebKit documents separate Web Inspector commands for technical investigation.

Name the object you need: a visible sentence, an element, a resource or a developer-tools panel. Each search surface has a different scope. Typing into the wrong field can produce an empty or irrelevant result even when the query itself is correct. Read the field and selected panel before changing your search words.

02Compare searches on a public page

1. Pick a harmless public page and find a visible term with normal page Find. Inspect the surrounding text so you know what that search returned.
2. If you already use developer tools, open the relevant inspector panel and note its separate search context. Return focus to the webpage before continuing to read. Do not modify an unfamiliar live application just to practise a command. The aim is to understand where input goes and what the results represent.

03Check details before sharing captures

Developer tools can show URLs, request details and private application state. Review any screenshot before sharing it, and avoid logged-in personal pages as public examples.

A shortcut reference cannot tell you whether an implementation is secure or a captured request is safe to publish. Inspector commands depend on the browser version and panel. When results differ from your expectation, check focus and scope before concluding that the resource does not exist.