Geolocation
The location prompt is a browser chrome UI, not page DOM — clicking "Allow" isn't something a locator can reach. Real tools handle this at the automation-context level instead: Playwright's context.grantPermissions(['geolocation']) plus context.setGeolocation({ latitude, longitude }), or Selenium's CDP Page.setGeolocationOverride. In CI, geolocation is usually denied or unavailable by default, so a robust test also has to handle the error path, not just the happy path.
1. Real browser geolocation
Calls navigator.geolocation.getCurrentPosition directly. Expect a permission prompt the first time, and a denial or timeout in most headless/CI setups unless it's pre-granted.
2. Simulated coordinates
Bypasses the permission prompt entirely — type coordinates and render them the same way a real fix would display. Useful for testing your display logic, or for confirming a geolocation override actually took effect.