simulator for safari browser

Safari Browser Testing

Browserling offers free online cross-browser testing in the Safari browser. At the moment, we offer Safari versions that run on Windows but very soon we'll also be adding Safari on macOS. The Windows Safari versions are installed on Windows 11, 10, 8.1, 8, 7, and XP. The installed Safari versions are from the official Apple installation packages and they are not fake browser emulators or simulators. To access Safari from Browserling, you don't have to install any additional software as Browserling is powered by HTML5 and JavaScript.

Try Safari in Browserling now!

Use the browser testing widget (below) to load an online Safari browser. Simply enter the address of a website that you want to open and press the "Test now!" button.

The free Browserling version offers 3 minutes of Safari testing on Windows 10 but to get unlimited minutes and access to all other operating systems, you'll have to get the developer plan .

Safari Testing FAQ

What is the latest safari version for windows.

The latest Windows Safari version is 5.1.5. You can access it via our quick browsing URL: browserling.com/browse/safari/5.1.5 .

What is the earliest Safari for Windows?

The earliest Windows Safari version is 4.0 and you can also access it via our quick browsing URL: browserling.com/browse/safari/4.0 .

Does Apple still maintain the Windows port of Safari?

No, Apple stopped maintaining Windows Safari after version 5.1.5

Do you offer Safari testing on macOS?

We're working on it! We don't have Safari on macOS yet but it's one of our top priority tasks to add it. Stay tuned!

Do you offer Safari testing on iPhones?

Offering Safari browser testing on iPhones is also one of our top tasks and we're working on it!

What browser engine does Safari use?

Safari is based on the WebKit browser engine. WebKit is also used by Chrome , Edge , and Opera browsers.

Do you run a Safari emulator?

No, we installed Safari from the official Apple installation package and it runs on a real computer. It's not an emulator nor a simulator but a real browser.

Can you help us with an issue on our website in Safari?

We'd love to help. We have been solving cross-browser testing problems for over 10 years and know everything there is about the Safari browser. Please email us at [email protected] and we'll help you with your website issue in Safari.

What is the Live Safari API?

It's a technology that we created. It lets you embed a Safari in your own project (a website or a webapp). Take a look at the Live API page that shows how it works.

For any other questions about cross-browser testing in Safari please contact us at [email protected] or use our contact form .

See how your page looks on the iPhone

• Cross Browser Testing
• Live Testing
• Visual Testing
• Smart-TV Testing
• Automated App Testing
• Live App Testing
• Codeless Automation
• Documentation

Superfast, Live Cross Browser Testing

Manually control any browser in our cloud from your own browser. Get instant access to real browsers and see how your website looks and behaves across multiple platforms.

Trusted by some of the world's most innovative companies

5200+ browser and device combinations.

All browsers come equipped with native debugging tools.

Adjust the screen-resolution on the fly or resize your browser to do responsive testing.

Run your tests against up-to-date beta and dev builds.

Instant access to any browser on Mac, Linux, Windows and Mobile.

Mobile Testing

Manually test your website on iOS and Android devices, straight from your own browser.

With TestingBot you can test your website on iOS and Android, take screenshots and rotate the device.

Take screenshots, rotate the screen, pinch-to-zoom and access debugging tools like Safari Developer Tools and Chrome DevTools to debug your website on mobile.

Quality through coverage

We provide one-click access to real browsers, running on real macOS, Windows and Linux platforms. From Windows 7 to Windows 11, macOS Sierra to Ventura and the latest Linux Ubuntu - we've got you covered.

Test across IE8 to IE11 and every version of Edge, Chrome, Safari, Firefox and Opera. Copy and paste data from your computer to the remote browser without any plugins.

Identify and fix bugs faster

Share your Live browser session with a co-worker to reproduce bugs and assist in debugging. Use the integrated Developer Tools to inspect your website and identify CSS/JS issues.

Take screenshots for any screen-resolution, platform and browser configuration.

A video and different logs are recorded during your manual testing, which you can download and share.

Test Staged Websites

Use our secure tunnel to quickly and easily test your staging website on all browsers.

Test data and websites from behind your firewall on the TestingBot cloud.

Sign up for a Free Trial

Start testing your apps with TestingBot.

No credit card required!

Freelance iOS, macOS, Apple Watch, and Apple TV Developer

Web inspector on ios devices and simulators.

Want to keep up to date? Sign up to my free newsletter which will give you exclusive updates on all of my projects along with early access to future apps.

Over the past few weeks I’ve worked on a number of projects that have necessitated me working with HTML and JavaScript be that via Safari on iOS, an SFSafariViewController, or in an embedded WKWebView. In all of these cases, I’ve needed to dive into the DOM to see what styles are being applied to certain elements or dig into a JavaScript Console to work out why some code isn’t working. On desktop, this is trivial as Safari has a Web Inspector panel built in similar to other browsers. It turns out it is also trivial on mobile as the exact same tool can be used with both iOS simulators and physical devices.

If you select the ‘Develop’ tab from the menu bar of Safari on macOS, you’ll see a list of all of your connected devices and actively running simulators 1 . Drilling into this will then show all of the active web instances you can interact with; notice how the content within Safari has highlighted blue within the Simulator as I’ve moused over the twitter.com web instance above. When you click, a web inspector panel is then produced which allows you to make all the usual interrogations and changes you can within desktop Safari such as interacting with the console or changing CSS values of elements to see how they would look in realtime.

Here’s an example using a WKWebView within one of my client projects, Yabla Spanish :

Discovering that simulators and devices could be interacted with in this way has been a huge timesaver for me. Whilst developing Browser Note , I was constantly needing to tweak CSS values and investigate the current state of the DOM as websites have various tricks to try and make ads or cookie notices appear on top of all content (and the note needed to be on top at all times - you should totally take a look at Browser Note whilst you’re here). In doing this, I was then able to put this knowledge to use on no less than 3 client projects in the past month; this validates my theory that by working on your own side projects you can improve your efficiency when it comes to work projects.

There are a few caveats to be aware of when using the Web Inspector with an iOS device or simulator:

• If you want to use this on an actual device you’ll first need to enable the Web Inspector on iOS. To do this, go to the Settings app and then Safari > Advanced and toggle the Web Inspector on.
• Whilst the Web Inspector can interrogate WKWebView, it can only do this for apps you are running via Xcode. You cannot look at the WKWebView of apps you did not create nor of your own apps from TestFlight / the App Store. However, you can inspect debug builds installed via Xcode even if the debugger is not active (i.e. you build to the device then quit Xcode).
• Conversely, you can use the Web Inspector with any SFSafariViewController even if it is not in your own app.
• Whilst it is still possible to submit apps that use UIWebView, the web inspector will not work with them; it needs to be WKWebView .
• This also works for AppKit, SwiftUI, and Catalyst apps on macOS.

I use an “iDod” naming prefix for all of my devices; a throwback pun to my first Apple product, the iPod.  ↩︎

This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

Emulate and test other browsers

• 10 contributors

Your job doesn't end with making sure your site runs great across Microsoft Edge and Android. Even though the Device Emulation tool can simulate a range of other devices such as smart phones, we encourage you to check out solutions for emulation provided by other browsers.

When you don't have a particular device, or want to do a spot check on something, the best option is to emulate the device right inside your browser.

Device emulators and simulators enable you to mimic your development site on a range of devices, from your workstation.

Cloud-based emulators enable you to automate unit tests for your site across different platforms.

Browser emulators

Browser emulators are great for testing the responsiveness of a site. But a browser emulator doesn't emulate differences in API, CSS support, and certain behaviors that manifest only on a mobile browser on an actual device. Test your site on browsers running on real devices, to be certain everything behaves as expected.

Firefox Responsive Design View

Firefox has a responsive design view that encourages you to stop thinking in terms of specific devices and instead explore how your design changes at common screen sizes, or on your own screen size by dragging the edges of the window.

EdgeHTML emulation

To emulate Windows Phones, use the Microsoft Edge (EdgeHTML) built-in emulation .

Use IE 11 Emulation to simulate how your page might look in older versions of Internet Explorer.

Device emulators and simulators

Device simulators and emulators simulate not just the browser environment but the entire device. Each simulator is useful to test things that require OS integration, such as form input with virtual keyboards.

Android emulator

At the moment, there is no way to install Microsoft Edge on an Android emulator. However, you can use the Android Browser, the Chromium Content Shell, and Firefox for Android, which we review later in this article. Chromium Content Shell runs the same Chromium rendering engine as Microsoft Edge, but comes without browser-specific features.

The Android emulator comes with the Android SDK which you need to download as part of Android Studio . Then follow the instructions to set up a virtual device and start the emulator . After your emulator is booted, select the Browser icon, and test your site on the old Stock Browser for Android.

Chromium content shell on Android

To install the Chromium Content Shell for Android, keep your emulator running and run the following command:

Now you can test your site with the Chromium Content Shell.

Firefox on Android

Similar to the Chromium Content Shell, you can get an APK to install Firefox onto the emulator.

Download the correct .apk file .

To install the file onto an open emulator or connected Android device, run the following command:

iOS simulator

The iOS simulator for Mac OS X comes with Xcode, which you install from the App Store .

When you are done, learn how to work with the simulator through Apple Developer documentation .

To avoid having to open Xcode every time you want to use the iOS Simulator, open it, right-click the iOS Simulator icon in your dock, and then select Keep in Dock . Now just click the icon whenever you need it.

Microsoft Edge (EdgeHTML)

If you need to test your website or app with Microsoft browsers and don't have the necessary versions of Windows to do so, you can use BrowserStack, which supports testing of many combinations of Microsoft browsers and operating systems both past and present. For example, you can test all versions of Microsoft Edge (Chromium) from version 80 onwards, and Microsoft Edge (EdgeHTML) versions 15 through 18. Testing of Microsoft Edge is free on BrowserStack. For more information, see Microsoft Edge Browser Testing at BrowserStack.

Cloud-based emulators and simulators

If you aren't able to use the emulators and you don't have access to real devices, then cloud-based emulators are the next-best thing. A big advantage of cloud-based emulators over real devices and local emulators is that you can automate unit tests for your site across different platforms.

The following list is a sample of cloud-based emulators and testing sites. Review the descriptions for features or capabilities to consider when selecting a testing site. Conduct your own search to find the best cloud-based emulator for your needs.

BrowserStack helps you perform manual testing. You select an operating system, a browser version, a device type, and a URL to browse, and then BrowserStack spins up a hosted virtual machine that you can interact with. You can run multiple emulators in the same screen, to test the look and feel of your app across multiple devices at the same time.

Mobileum doesn't use emulators, but real devices which you can control remotely. This is useful when you need to reproduce a problem on a specific device and an issue might not appear in some reports.

HeadSpin helps you perform manual cross-browser testing on thousands of real devices, browsers, and operating systems. You can record videos of complex bugs and share them through integration such as Slack, JIRA, and more. Fast forward your go-to-market launch by testing in parallel.

LambdaTest helps you perform manual cross-browser testing on a combination of various browsers and operating systems. You can record videos of complex bugs and share them through integration such as Microsoft Teams, Slack, and more. You can speed-up your testing by running tests in parallel.

SauceLabs enables you to run unit tests inside of an emulator, which can be useful for scripting a flow through your site and watching the video recording of this afterwards on various devices. You can also do manual testing with your site.

TestingBot helps you do both manual testing and automated testing on various browser and operating system combinations. Test both your websites and mobile apps on TestingBot's emulators and physical devices.

Portions of this page are modifications based on work created and shared by Google and used according to terms described in the Creative Commons Attribution 4.0 International License . The original page is found here and is authored by Meggin Kearney (Technical Writer) and Paul Bakaus (Open Web Developer Advocate at Google | Tools, Performance, Animation, UX).

Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback .

Submit and view feedback for

Additional resources

• Español – América Latina
• Português – Brasil
• Tiếng Việt
• Chrome DevTools

Emulate and Test Other Browsers

Your job doesn't end with ensuring your site runs great across Chrome and Android. Even though Device Mode can simulate a range of other devices like iPhones, we encourage you to check out other browsers solutions for emulation.

• When you don't have a particular device, or want to do a spot check on something, the best option is to emulate the device right inside your browser.
• Device emulators and simulators let you mimic your development site on a range of devices from your workstation.
• Cloud-based emulators let you automate unit tests for your site across different platforms.

Browser emulators

Browser emulators are great for testing a site's responsiveness, but they don't emulate differences in API, CSS support, and certain behaviors that you'd see on a mobile browser. Test your site on browsers running on real devices to be certain everything behaves as expected.

Firefox' Responsive Design View

Firefox has a responsive design view that encourages you to stop thinking in terms of specific devices and instead explore how your design changes at common screen sizes or your own size by dragging the edges.

Edge's F12 Emulation

To emulate Windows Phones, use Microsoft Edge's built-in emulation .

Since Edge does not ship with legacy compatibility, use IE 11's Emulation to simulate how your page would look in older versions of Internet Explorer.

Device emulators and simulators

Device simulators and emulators simulate not just the browser environment but the entire device. They're useful to test things that require OS integration, for example form input with virtual keyboards.

Android Emulator

Stock Browser in Android Emulator

At the moment, there is no way to install Chrome on an Android emulator. However, you can use the Android Browser, the Chromium Content Shell and Firefox for Android which we'll cover later in this guide. Chromium Content Shell uses the same Chrome rendering engine, but comes without any of the browser specific features.

The Android emulator comes with the Android SDK which you need to download from here . Then follow the instructions to setup a virtual device and start the emulator .

Once your emulator is booted, click on the Browser icon and you'll be able to test your site on the old Stock Browser for Android.

Chromium Content Shell on Android

Android Emulator Content Shell

To install the Chromium Content Shell for Android, leave your emulator running and run the following commands at a command prompt:

Now you can test your site with the Chromium Content Shell.

Firefox on Android

Firefox Icon on Android Emulator

Similar to Chromium's Content Shell, you can get an APK to install Firefox onto the emulator.

Download the right .apk file from https://ftp.mozilla.org/pub/mozilla.org/mobile/releases/latest/ .

From here, you can install the file onto an open emulator or connected Android device with the following command:

iOS Simulator

The iOS simulator for Mac OS X comes with Xcode, which you can install from the App Store .

When you're done, learn how to work with the simulator through Apple's documentation .

Modern IE VM

Modern.IE Virtual Machines let you access different versions of IE on your computer via VirtualBox (or VMWare). Choose a virtual machine on the download page here .

Cloud-based emulators and simulators

If you can't use the emulators and don't have access to real devices, then cloud-based emulators are the next best thing. A big advantage of cloud-based emulators over real devices and local emulators is that you can automate unit tests for your site across different platforms.

• BrowserStack (commercial) is the easiest to use for manual testing. You select an operating system, select your browser version and device type, select a URL to browse, and it spins up a hosted virtual machine that you can interact with. You can also fire up multiple emulators in the same screen, letting you test how your app looks and feels across multiple devices at the same time.
• SauceLabs (commercial) allows you to run unit tests inside of an emulator, which can be really useful for scripting a flow through your site and watch the video recording of this afterwards on various devices. You can also do manual testing with your site.
• Device Anywhere (commercial) doesn't use emulators but real devices which you can control remotely. This is very useful in the event where you need to reproduce a problem on a specific device and can't see the bug on any of the options in the previous guides.
• LambdaTest (commercial) will help you to perform manual cross browser testing on a combination of 2000+ browsers & operating systems. Users will be able to record video of complex bugs and eve share it via integrations like MS Teams, Slack and more. Users can speed-up their testing by running tests in parallel.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2015-04-13 UTC.

Demo Appetize.io's online web based iOS Simulators and Android Emulators directly in your browser.

How-To Geek

I tried browsing the web with safari 1.0, here's how it went.

Hands-on with Apple's first web browser.

Key Takeaways

• Safari 1.0 was released in 2003 to replace Internet Explorer on the Mac.
• It was lacking some features compared to other web browsers, but it was fast and minimalist.
• Safari 1.0 is not compatible with most modern websites.

Safari was introduced in 2003 as Apple's replacement for Internet Explorer on the Mac, and it has continued to evolve since then as the default browser on all Apple devices. Let's take a deep dive into the browser that started it all: Safari 1.0.

The first version of Safari was released on June 23rd, 2003 , following a public beta that reached nearly five million downloads. The initial version was an optional download for Macs running Mac OS X 10.2 Jaguar , and it was later bundled with Mac OS X 10.3 Panther . Apple continued shipping Safari with every new Mac operating system, continuing to the present day with new releases of macOS.

Hello, Safari

Safari is a core system application on Mac computers, so you can't (easily) use older versions on newer operating systems that have a newer Safari version already installed. In the name of science, I fired up my trusty 1999 PowerMac G3, created a new drive partition, and installed a fresh copy of Mac OS X 10.3 Panther. That release shipped with Safari version 1.1, so this isn't technically the first public version, but it's close enough.

Safari 1.0 is a far cry from modern versions of Apple's web browser, but there are some familiar interface elements. The top bar has the back, forward, reload, and bookmark buttons that are still present in today's web browsers, but the address bar and web search are two separate text fields.

Google Chrome helped popularize the idea of a combined address and search bar when it was released in 2009, but before that, most web browsers had the same split text fields. On that note, Google is the default search engine, and I didn't see an option anywhere to change it.

Safari 1.0 isn't just minimalist by today's standards. This new Mac OS X installation also came with Internet Explorer 5 for Mac, which has a much more cluttered design with a sidebar, status bar, and more buttons at the top of the window. You could click a button on the sidebar to hide most of that for distraction-free browsing, but Safari is less complicated out of the box.

Most of the other browsers from this time, like Opera, Netscape, and the Mozilla Application Suite, were similarly feature-packed. The first version of Firefox arrived in 2004, the year after Safari, with a simplified feature set and a focus on web browsing. There is support for tabbed browsing in Safari 1.0, but it's not enabled by default.

There's also a bookmarks manager for organizing your favorite sites and pages, accessible from the menu bar or the bookmarks button in the bookmarks bar. The default bookmarks are a fun look back at the early-2000s internet, with links to Amazon, PayPal, BBC News, MapQuest, Monster.com, and other sites.

The preferences panel has some options for how windows open, where to save files and pages, turning on tabbed browsing, managing plugins, and deleting browsing cookies. There's also an AutoFill feature that can fill in web forms with information from your Address Book.

I also noticed this early version of Safari doesn't have an Inspect Element option, or seemingly any other web development features. You can view the HTML source code for a page, but that's it.

Surf Like It's 2003

So, what can you actually do with Safari 1.0 in 2024? Well, not a lot. This is a twenty-year-old web rendering engine, with no support for modern HTML and CSS layout features, HTML5 video, or most JavaScript features. Every site that loads over HTTPS (SSL) shows security warnings or refuses to load at all.

The main Google home page works, but the search results use a broken mobile layout. CNN, Apple.com, Wikipedia, eBay, and BBC News don't load at all. Amazon made the browser freeze for about a minute, complete with the spinning beachball of death, then loaded a page with just text and no styling or images.

There are a few websites designed specifically for older browsers, though. The FrogFind search engine created by Action Retro on YouTube works well here, which downgrades modern sites to simpler text-based layouts.

FrogFind doesn’t always work well, but it does turn websites like Wikipedia from completely unusable to readable.

Looking Back at Tomorrow

You can’t use Safari 1.0 for typical web browsing anymore, but it’s still a fascinating look at Apple’s vision for the future of web browsing. It wasn’t a feature-packed internet suite, like Netscape and Mozilla, or a super-customizable application like Opera. It was a fast, simple, and focused web browser, built on top of the modern KHTML engine from KDE’s Konqueror project.

Even though Safari wasn’t a perfect experience in its early days, the response from Mac owners was generally positive. Macworld said in 2003 , “Safari loaded pages faster than Internet Explorer in four out of five tests — in some cases, almost twice as fast.” The review from CNET for the 1.0 release said, “We encountered only minor bugs, usually related to JavaScript errors, though less so than the beta versions. Overall, Safari performed well.”

Safari went on to serve as the default browser for the iPhone and iPad, and there was a short-lived Windows version starting in 2007 . Safari’s underlying WebKit engine has also helped shape the internet we know today. WebKit was used by Google Chrome for years until Google forked it to create the Blink engine , which is now used by Microsoft Edge, Google Chrome, Vivaldi, and other web browsers.

For now, though, I’m happy to get back to a functioning modern web browser.

• a. Send us an email
• b. Anonymous form
• Buyer's Guide
• Upcoming Products
• Tips / Contact Us
• Podcast Instagram Facebook Twitter Mastodon YouTube Notifications RSS Newsletter

Apple Releases Safari Technology Preview 194 With Bug Fixes and Performance Improvements

Apple last week released a new update for Safari Technology Preview , the experimental browser Apple first introduced in March 2016. Apple designed the ‌Safari Technology Preview‌ to test features that may be introduced into future release versions of Safari.

The current ‌Safari Technology Preview‌ release is compatible with machines running macOS Ventura and macOS Sonoma , the latest version of macOS that Apple released in September 2023.

The ‌Safari Technology Preview‌ update is available through the Software Update mechanism in System Preferences or System Settings to anyone who has downloaded the browser . Full release notes for the update are available on the Safari Technology Preview website .

Apple's aim with ‌Safari Technology Preview‌ is to gather feedback from developers and users on its browser development process. ‌Safari Technology Preview‌ can run side-by-side with the existing Safari browser and while designed for developers, it does not require a developer account to download.

Get weekly top MacRumors stories in your inbox.

Popular Stories

iMessage Down for Some Users [Update: Service Restored]

Troubling iOS 17.5 Bug Reportedly Resurfacing Old Deleted Photos

iPhone 16 Pro Max Looks This Much Bigger Beside iPhone 15 Pro Max

iOS 17.5 Bug May Also Resurface Deleted Photos on Wiped, Sold Devices

OLED iPad Pro Users Report 'Grainy' Displays, But It May Not Be a Defect

iPhone Emulators on the App Store: Game Boy, N64, PS1, PSP, and More

Next article.

Our comprehensive guide highlighting every major new addition in iOS 17, plus how-tos that walk you through using the new features.

Apple News+ improvements, cross-platform tracker alerts, website app downloads for the EU, and more.

Get the most out your iPhone 15 with our complete guide to all the new features.

A deep dive into new features in macOS Sonoma, big and small.

Apple's annual Worldwide Developers Conference will kick off with a keynote on June 10.

Expected to see new AI-focused features and more. Preview coming at WWDC in June with public release in September.

AI-focused improvements, new features for Calculator and Notes, and more.

Action button expands to all models, new Capture button, camera improvements, and more.

Other Stories

3 days ago by Tim Hardwick

4 days ago by Tim Hardwick

6 days ago by Juli Clover

6 days ago by Tim Hardwick

Apple geofences third-party browser engine work for EU devices

Rival coders must have europe-based staff to build and test non-webkit surfing.

Exclusive   Apple's grudging accommodation of European law – allowing third-party browser engines on its mobile devices – apparently comes with a restriction that makes it difficult to develop and support third-party browser engines for the region.…

The Register has learned from those involved in the browser trade that Apple has limited the development and testing of third-party browser engines to devices physically located in the EU. That requirement adds an additional barrier to anyone planning to develop and support a browser with an alternative engine in the EU.

It effectively geofences the development team. Browser-makers whose dev teams are located in the US will only be able to work on simulators. While some testing can be done in a simulator, there's no substitute for testing on device – which means developers will have to work within Apple's prescribed geographical boundary.

Prior to iOS 17.4, Apple required all web browsers on iOS or iPadOS to use Apple's WebKit rendering engine. Alternatives like Gecko (used by Mozilla Firefox) or Blink (used by Google and other Chromium-based browsers) were not permitted. Whatever brand of browser you thought you were using on your iPhone, under the hood it was basically Safari.

Browser makers have objected to this for years, because it limits competitive differentiation and reduces the incentive for Apple owners to use non-Safari browsers.

Apple's designation under Europe's Digital Markets Act (DMA) as a gatekeeper for the App Store, iOS, Safari, and just recently iPadOS forced Cupertino to make concessions.

One such allowance – realized in iOS 17.4 – was letting iOS (and subsequently iPadOS) apps in the EU use alternative browser engines.

But rivals have complained that Apple's concessions are designed – as Mozilla put it – to make it "as painful as possible for others to provide competitive alternatives to Safari."

That can be seen in Apple's extensive list of requirements to offer a third-party browser engine on iOS in the EU.

Parisa Tabriz, VP of engineering and general manager of Chrome at Google, dismissed Apple's rule changes earlier this year. "Apple isn't serious about supporting web browser or engine choice on iOS," Tabriz wrote in February. "Their strategy is overly restrictive, and won't meaningfully lead to real choice for browser developers."

When Apple announced its plan to make changes in response to DMA in January, developers expressed concern that supporting a separate EU browser might be a problem. And those concerns persist.

"The contract terms are bonkers and almost no vendor I'm aware of will agree to them," lamented one industry veteran familiar with the making of browsers in response to an inquiry from The Register.

"Even folks that may have signed something to be able to prototype can't ship under the constraints Apple's trying to impose. They're so broad and sweeping as to try to duck most of the DMA by contract … which is certainly bold."

In March, the European Commission opened an investigation into Apple based on concerns that Cupertino's "steering" rules and browser choice screen fell short of DMA requirements.

"By blocking browser engineers across the globe from working on their real browsers unless they are physically located in the EU, Apple is preventing them from being able to compete or perhaps even ship on iOS," declared Alex Moore, executive director of Open Web Advocacy, in a note to The Register.

"This is clearly absurd, has no reasonable justification and can only be described as malicious compliance. As a plausible scenario, imagine as a browser vendor you have a security issue but your top expert on that type of vulnerability is in the US. They have to fly to the EU so they can test and fix on a real device?

"At a minimum, Apple should issue guidance that this is a misunderstanding and that browser vendor test devices are exempt."

Asked about Apple's geofencing of devices for development, an Opera spokesperson replied that it hadn't heard about the issue – but that's not surprising given that the organization is headquartered in the EU.

Jon von Tetzchner, CEO of Vivaldi, also admitted he hadn't heard about the requirement. "Our dev team is all based in the EEA – mostly Norway and Iceland – so I presume this would not have applied to us," he explained. "But again, I cannot see how they could have a rule like that.

"I would think that would be seen as another anti-competitive move," he added.

"[Apple's] team is in the US and so are the teams for Microsoft, Google, Mozilla and most of the other larger browser companies."

Google and Mozilla didn't immediately respond to requests for comment. Nor did Apple – which seldom does.

Mozilla and Google have explored versions of Firefox and Chrome for iOS based on non-WebKit engines, but have yet to release anything. Firefox users have requested a Gecko-based version of Firefox for iOS, but are yet to receive any release commitment. ®

About the security content of Safari 17.5

This document describes the security content of Safari 17.5.

About Apple security updates

For our customers' protection, Apple doesn't disclose, discuss, or confirm security issues until an investigation has occurred and patches or releases are available. Recent releases are listed on the  Apple security releases page.

Apple security documents reference vulnerabilities by  CVE-ID  when possible.

For more information about security, see the  Apple Product Security  page.

Safari 17.5

Released May 13, 2024

Available for: macOS Monterey and macOS Ventura

Impact: An attacker with arbitrary read and write capability may be able to bypass Pointer Authentication

Description: The issue was addressed with improved checks.

WebKit Bugzilla: 272750 CVE-2024-27834: Manfred Paul (@_manfp) working with Trend Micro's Zero Day Initiative

Additional recognition

Safari Downloads

We would like to acknowledge Arsenii Kostromin (0x3c3e) for their assistance.

Information about products not manufactured by Apple, or independent websites not controlled or tested by Apple, is provided without recommendation or endorsement. Apple assumes no responsibility with regard to the selection, performance, or use of third-party websites or products. Apple makes no representations regarding third-party website accuracy or reliability. Contact the vendor for additional information.

Start a discussion in Apple Support Communities

Microsoft really wants you to start using its Edge web browser

• Microsoft is adding an AI feature to its Edge web browser in an apparent bid to win more users.
• Rival web browsers Chrome and Safari are far more popular than Edge, StatCounter data shows. 
• Google added AI features for its browser in January, and Apple is rumored to roll some out too. 

Microsoft might be the most valuable listed company, but it's failed to get very many people to abandon Chrome or Safari in favor of its own web browser.

However, Edge may become a little more enticing with the addition of a new AI feature.

Microsoft plans to launch an "AI theme generator" next month that will let users create their own browser themes by using a text prompter to create images.

Related stories

"Applying the theme includes setting the generated image on the Edge new tab page, and applying the image's dominant color to the browser frame," according to an update to its 365 road map.

Microsoft Edge launched in 2015 to rival web browsers Google Chrome and Apple's Safari. It was intended to replace Internet Explorer, which was retired in 2022 .

Chrome is the web browser for most internet users. Data from StatCounter shows the Google offering had a global market share of more than 65% in April. Safari had more than 18%, with Edge lagging behind on about 5%.

In January, Google announced three new generative AI features for Chrome. They include a browser theme generator, a tab organizer that suggests and creates tab groups based on a user's open tabs, and a tool called "Help Me Write" to assist users in writing pieces such as reviews.

According to Apple Insider, Apple is gearing up to launch an AI browser assistant called "Intelligent Search" that can automatically generate summaries of web pages by identifying subjects and key phrases. It's expected to be announced with the rollout of its latest iOS 18 update at its Worldwide Developers Conference next month.

Microsoft didn't immediately respond to a request for comment from Business Insider, made outside normal working hours.

• Main content