So not sure what changed but when I would click on an address in safari or the map it would take me to google or Apple Maps. Now it opens maps in a separate safari window and asks if I want to open maps…the goes to the App Store. What’s going on?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Maps & Safari Issue
- Thread starter Poppaduck
- Start date
- Sort by reaction score
Which maOS version are you using?
As I understand it, it's the websites and the search engine that determine which map will open.
When I search for 1 Apple Way, Cupertino CA in Safari with Duck Duck Go as the search engine, it goes to an Apple Maps link. When I search the same address using Google search, it goes to a Google Maps link.
Are you by any chance hitting command-click that would open the link in a separate tab?
When you say it goes to the App Store, does this happen only for a Google maps link?
As I understand it, it's the websites and the search engine that determine which map will open.
When I search for 1 Apple Way, Cupertino CA in Safari with Duck Duck Go as the search engine, it goes to an Apple Maps link. When I search the same address using Google search, it goes to a Google Maps link.
Are you by any chance hitting command-click that would open the link in a separate tab?
When you say it goes to the App Store, does this happen only for a Google maps link?
Every hyperlink can be configured (by the web page designer) to open in a new browser tab. The relevant optional hyperlink attribute is, I believe, target="_blank". When you open a hyperlink, the server first returns a header before the actual content is delivered. Depending on the server's behaviour, it can formulate what it believes is an appropriate "response type" header that tells your browser how to open the content. This is how you can, for example, automatically open a link to spreadsheet content in a spreadsheet application rather than a video player. The browser may also have its own rules about how it wants to play. For example, when your browser makes a web request for an image file (let's say a jpeg), the server should prefix the returned content with an appropriate response type header such as "image/jpeg". But the server is not obliged to do so. If you request a URL ending .jpg the browser might reasonably assume you're asking for an image, regardless of any header the server might return.
So, in short, quite a few variables involved, and it's not completely straightforward.
