webkit in safari

Navigation Menu

Search code, repositories, users, issues, pull requests..., provide feedback.

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly.

To see all available qualifiers, see our documentation .

• Notifications

Home of the WebKit project, the browser engine used by Safari, Mail, App Store and many other applications on macOS, iOS and Linux.

WebKit/WebKit

Folders and files, repository files navigation.

WebKit is a cross-platform web browser engine. On iOS and macOS, it powers Safari, Mail, iBooks, and many other applications. For more information about WebKit, see the WebKit project website .

Trying the Latest

On macOS, download Safari Technology Preview to test the latest version of WebKit. On Linux, download Epiphany Technology Preview . On Windows, you'll have to build it yourself.

Reporting Bugs

• Search WebKit Bugzilla to see if there is an existing report for the bug you've encountered.
• Create a Bugzilla account to report bugs (and comment on them) if you haven't done so already.
• File a bug in accordance with our guidelines .

Once your bug is filed, you will receive email when it is updated at each stage in the bug life cycle . After the bug is considered fixed, you may be asked to download the latest nightly and confirm that the fix works for you.

Getting the Code

Run the following command to clone WebKit's Git repository:

Building WebKit

Building for apple platforms.

Install Xcode and its command line tools if you haven't done so already:

• Install Xcode Get Xcode from https://developer.apple.com/downloads . To build WebKit for OS X, Xcode 5.1.1 or later is required. To build WebKit for iOS Simulator, Xcode 7 or later is required.
• Install the Xcode Command Line Tools In Terminal, run the command: xcode-select --install

Run the following command to build a macOS debug build with debugging symbols and assertions:

For performance testing, and other purposes, use --release instead.

Embedded Builds

To build for an embedded platform like iOS, tvOS, or watchOS, pass a platform argument to build-webkit .

For example, to build a debug build with debugging symbols and assertions for embedded simulators:

or embedded devices:

where platform is ios , tvos or watchos .

Using Xcode

You can open WebKit.xcworkspace to build and debug WebKit within Xcode. Select the "Everything up to WebKit + Tools" scheme to build the entire project.

If you don't use a custom build location in Xcode preferences, you have to update the workspace settings to use WebKitBuild directory. In menu bar, choose File > Workspace Settings, then click the Advanced button, select "Custom", "Relative to Workspace", and enter WebKitBuild for both Products and Intermediates.

Building the GTK Port

For production builds:

For development builds:

For more information on building WebKitGTK, see the wiki page .

Building the WPE Port

Building windows port.

For building WebKit on Windows, see the WebKit on Windows page .

Running WebKit

With safari and other macos applications.

Run the following command to launch Safari with your local build of WebKit:

The run-safari script sets the DYLD_FRAMEWORK_PATH environment variable to point to your build products, and then launches /Applications/Safari.app . DYLD_FRAMEWORK_PATH tells the system loader to prefer your build products over the frameworks installed in /System/Library/Frameworks .

To run other applications with your local build of WebKit, run the following command:

iOS Simulator

Run the following command to launch iOS simulator with your local build of WebKit:

In both cases, if you have built release builds instead, use --release instead of --debug .

Linux Ports

If you have a development build, you can use the run-minibrowser script, e.g.:

Pass one of --gtk , --jsc-only , or --wpe to indicate the port to use.

Congratulations! You’re up and running. Now you can begin coding in WebKit and contribute your fixes and new features to the project. For details on submitting your code to the project, read Contributing Code .

Contributors 997

Introduction to WebKit ¶

WebKit is an open-source Web browser engine. It’s a framework in macOS and iOS, and used by many first party and third party applications including Safari, Mail, Notes, Books, News, and App Store.

What is WebKit? ¶

The WebKit codebase is mostly written in C++ with bits of C and assembly, primarily in JavaScriptCore, and some Objective-C to integrate with Cocoa platforms.

It primarily consists of the following components, each inside its own directory in Source :

• bmalloc - WebKit’s malloc implementation as a bump pointer allocator. It provides an important security feature, called IsoHeap, which segregates each type of object into its own page to prevent type confusion attacks upon use-after-free.
• WTF - Stands for Web Template Framework. WebKit’s template library. The rest of the WebKit codebase is built using this template library in addition to, and often in place of, similar class templates in the C++ standard library. It contains common container classes such as Vector, HashMap (unordered), HashSet, and smart pointer types such as Ref, RefPtr, and WeakPtr used throughout the rest of WebKit.
• Interpreter - This tier reads and executes instructions in byte code in C++.
• Baseline JIT - The first Just In Time compiler tier serves as the profiler as well as a significant speed up from the interpreter.
• DFG JIT - Data Flow Graph Just In Time compiler uses the data flow analysis to generate optimized machine code.
• FTL JIT - Faster than Light Just In Time compiler which uses B3 backend . It’s the fastest tier of JSC. JavaScriptCode also implements JavaScriptCore API for macOS and iOS applications.
• Document Object Model - This is the tree data structure we create from parsing HTML.
• Render Tree - This tree represents the visual representation of each element in DOM tree computed from CSS and also stores the geometric layout information of each element.
• WebCore/PAL and WebCore/platform - Whilst technically a part of WebCore, this is a platform abstraction layer for WebCore so that the rest of WebCore code can remain platform independent / agnostic across all the platforms WebKit can run on: macOS, iOS, Windows, Linux, etc... Historically, most of this code resided in WebCore/platform. There is an ongoing multi-year project to slowly migrate code to PAL as we remove the reverse dependencies to WebCore.
• WebKitLegacy (a.k.a. WebKit1) - This layer interfaces WebCore with the rest of operating systems in single process and implements WebView on macOS and UIWebView on iOS.
• UI process - This is the application process. e.g. Safari and Mail
• WebContent process - This process loads & runs code loaded from websites. Each tab in Safari typically has its own WebContent process. This is important to keep each tab responsive and protect websites from one another.
• Networking process - This process is responsible for handling network requests as well as storage management. All WebContent processes in a single session (default vs. private browsing) share a single networking session in the networking process.
• WebInspector / WebDriver - WebKit’s developer tool & automation tool for Web developers.

What are Safari experimental WebKit features on iOS?

Modified Nov. 3, 2023, 8:44 p.m. By Maxime Levesque

The Safari advanced settings on iOS contain a specific menu called Experimental WebKit features. What are these settings? Should I turn off them? I’ll explain what are those experimental features and what to do with them.

Safari experimental WebKit features on iOS are mostly useful for developers that want to try some of the new features implemented in Safari but not activated by default yet or that have been recently enabled. Each entry in this menu corresponds to a specific feature, enabling or disabling it could change the behavior of your Safari browser, should you do it? I’ll answer this and will also detail each of these features.

What are Safari experimental WebKit features useful for?

Should i turn off experimental wekkit features, how to reset experimental webkit features.

Web development is evolving very quickly, new technologies are out every month, and new features are released in every new version of Safari, the Apple web browser . It can be very complicated for the developers to be sure that the web applications they develop are compatible with these new features, or if the new technologies released can be used inside their web applications to make them even better.

The Safari experimental WebKit features help the developers to test the features that will be released in the next version of Safari, or a new technology available but not so much used yet. The developers can enable or disable each of these WebKit features during their tests.

You can find more information on Safari resources here.

The short answer is no, you should not change anything in this menu if you do not know what is the meaning of the feature.

Some of these features are enabled by default, it can be because Apple wants to allow web developers to try what happens when they disable it, or because the feature has been enabled in one of the last versions of Safari. Disabling a feature could change the behavior of Safari and therefore add some bugs you could not understand.

These features are focused on web development and you should not have to change anything in this menu. But a bad update could be released with bugs, which could decrease the battery health faster for example. This is the only case where a manual change from you could be required until Apple releases a fix, but it’s rarely really needed.

If you or someone else changed anything in this menu without understanding the meaning of the feature, you should reset the values to the default ones.

• Open settings on your iPhone or iPad
• Open the Safari settings
• Scroll to the bottom and open Advanced
• Scroll to the bottom and open Experimental Features/

• Scroll to the very bottom and click on Reset All to Defaults

• That’s it, all the experimental WebKit features values have been reset to default ones

What experimental WebKit features should be on?

If you do not want to reset all the values to defaults and just want to be sure what are the values at default, here is the list of enabled features :

The experimental WebKit features that should be on in iOS 17 are :

• :focus-visible pseudo-class
• :has() pseudo-class
• AccessHandle API
• Aspect ratio of </img> from width and height
• Async clipboard API
• Blank anchor target implies rel=noopener
• Block top-level redirects by third-party iframes
• BroadcastChannel Origin
• CSS Accent Color
• CSS Aspect Ratio
• CSS Cascade Layers
• CSS Color 4 Color Types
• CSS Container Queries
• CSS Containment
• CSS Gradient Premultiplied Alpha Interpolation
• CSS Individual Transform Properties
• CSS Motion Path
• CSS Overscroll Behavior
• CSS overflow: clip support
• CSS subgrid support
• CSS text-align-last property
• CSSOM View Smooth Scrolling
• Canvas Color Spaces
• Cross-Origin-Embedder-Policy
• Cross-Origin-Opener-Policy
• Defer async scripts until DOMContentLoaded or first-paint
• Dialog Element
• Disallow sync XHR during page dismissal
• Experimental MediaSource Inline Painting
• Fetch API Request KeepAlive
• File System Access API
• Form requestSubmit
• GPU Process: DOM Rendering
• GPU Process: WebGL
• Generic Text Track Cue API
• HDR Media Capabilities
• ImageBitmap
• In-Process Cookie Cache
• Intersection Observer
• Lazy image loading
• Mask WebGL Strings
• Media Capabilities Extensions
• Media Session API
• MediaRecorder
• NSURLSession WebSocket
• Opus audio decoder
• Paint Timing
• PerformanceNavigationTiming
• Permissions API
• Prefer Page Rendering Updates near 60fps
• Private Click Measurement Fraud Prevention
• Referrer Policy attribute
• Remote Playback API
• RequestVideoFramCallback
• Resize Observer
• Resolution media feature
• Service Worker Navigation Preload
• SharedWorker
• SpeechRcognition API
• Storage API
• Swap Processes on Cross-Site Navigation
• Synthetic Editing Commands
• TranformStream API
• UserGesture Promise Propagation
• Visual Viewport API
• Vorbis audio decoder
• Web Animations composite operations
• Web Animations mutable timelines
• Web Autentication
• Web Locks API
• Web Share API Level 2
• WebGL via Metal
• WebRTC Encoded Transform API
• WebRTC H264 LowLatency encoder
• WebRTC Platform TCP Sockets
• WebRTC Platform UDP Sockets
• WebRTC Sockets Proxying
• WebRTC VP9 profile 0 codec
• WebRTC VP9 profile 2 codec
• Wheel Event gestures become non-blocking
• Wheel Event listeners on the root made passive
• inert attribute

Maxime Levesque is a technical engineer with more than 5 years of professional experience. He is an expert in computer and phones, mostly on Apple products. Maxime is also the founder of TechBrowser.

Willy - Oct. 18, 2023, 12:44 p.m.

Carole coleman - oct. 22, 2023, 5:51 a.m., maxime levesque - moderator - oct. 22, 2023, 7:47 a.m., post your comment, lastest reviews.

The Best Podcast Microphones for iPhone

The Best External Microphones for iPhone

I’ve been able to test many different external microphones while recording videos but also audio-only using my iPhones.

The Best Mini Microphone for iPhone

As an audio equipment expert with extensive experience in testing various mini microphones for the iPhone, I'm excited to share my insights with you.

Lastest News

What is Journal, the new Apple application?

Apple's latest addition to its iOS ecosystem is the Journal app, introduced with the first beta of iOS 17.2, is now available for every user with the latest 17.2 update.

MacBooks Pro with M3 chip announced

IOS 17.1 RC now available for download

Apple just released the 17.1 release candidate update, which means the official 17.1 update should be release next week. Here is what’s new.

Latest Posts

6 Ways to Improve a MacBook's Speed

MacBooks are one of the best when it comes to excelling in the overall performance. However, similar to other devices, Macs are no exception when it comes to performance drop over time.

The Impact of iPhone Cases on Microphone Quality

As a phone enthusiast and a frequent user of various iPhone cases and accessories, I've noticed something interesting – these items can significantly affect the microphone quality of your iPhone

Understanding the Technical Specifications of iPhone Microphones

Today, I'm excited to chat about something that often goes unnoticed but is super important in our iPhones – the microphones.

Privacy Policy

Terms of Service

Cookie Policy

© 2023 SAS Vexilab, All rights reserved

Ads displayed using affimate.io

Apple touts major 60% leap in Safari and WebKit performance

Apple’s WebKit team has published a new blog post this week detailing how they’ve made significant upgrades to Safari’s performance over the last several months. The improvements come following the debut of Speedometer 3.0 in March, described as a “major step forward in making the web faster for all.”

Back in March, Apple, Google, and Mozilla teamed up to launch the new Speedometer 3 browser benchmark. The goal of Speedometer 3 is to “create a shared understanding of web performance so that improvements can be made to enhance the user experience.”

The results provided by Speedometer 3 offer more details on how the test “captures and calculates scores, show more detailed results and introduce an even wider variety of workloads.” Apple says:

The introduction of Speedometer 3.0 is a major step forward in making the web faster for all, and allowing Web developers to make websites and web apps that were not previously possible.

Apple’s WebKit team says that it has successfully improved Safari’s Speedometer 3.0 score by ~60% between the release of Safari 17.0 in September and Safari 17.4’s release in March. These improvements, Apple says, mean that developers can build websites and web apps that are faster than ever before:

With all these optimizations and dozens more, we were able to improve the overall Speedometer 3.0 score by ~60% between Safari 17.0 and Safari 17.4. Even though individual progressions were often less than 1%, over time, they all stacked up together to make a big difference. Because some of these optimizations also benefited Speedometer 2.1, Safari 17.4 is also ~13% faster than Safari 17.0 on Speedometer 2.1. We’re thrilled to deliver these performance improvements to our users allowing web developers to build websites and web apps that are more responsive and snappier than ever.

The full blog post has a ton of technical details on the work that has been done to optimize WebKit and Safari for Speedometer 3.0.

Follow Chance :  Threads ,  Twitter ,  Instagram , and  Mastodon . 

FTC: We use income earning auto affiliate links. More.

Check out 9to5Mac on YouTube for more Apple news:

Chance is an editor for the entire 9to5 network and covers the latest Apple news for 9to5Mac.

Tips, questions, typos to [email protected]

Manage push notifications

Which Experimental Webkit Features Should Be Turned On?

The Safari web browser, developed by Apple, offers a range of experimental features designed for developers to improve and debug their web experiences. These features are not meant for regular users, but they can be activated if necessary, especially when seeking technical support from Apple.

WebKit is the underlying technology that powers Safari, and it constantly evolves to support new web standards and provide better performance. With the introduction of iOS 12/11, Apple introduced Safari WebKit Experimental Features, allowing developers to explore and test new functionalities within their apps.

But which experimental features should you consider turning on? Let’s take a closer look at some of them:

1. Web Push on iOS and iPadOS: This feature enables websites to send push notifications directly to iOS and iPadOS devices. It enhances the user experience by keeping them updated with relevant information, such as news updates, promotions, or reminders.

2. Improvements for Web Apps: These experimental features aim to enhance the performance and functionality of web applications on Safari. They can provide developers with tools to optimize their apps, resulting in smoother and more responsive user experiences.

3. Web Components: Web Components are a set of web platform APIs that allow developers to create reusable custom elements for web applications. By enabling this experimental feature, developers can leverage these APIs to build modular and easily maintainable web components.

4. CSS Enhancements: Experimental CSS features can unlock new possibilities for web design and styling. These features often introduce cutting-edge techniques, such as new layout models, animations, or visual effects. Enabling these features can empower developers to create unique and visually appealing websites.

5. HTML Improvements: Safari’s experimental HTML features can provide developers with access to new HTML elements, attributes, and APIs. These additions can enhance the structure and functionality of web pages, allowing for more interactive and engaging user experiences.

6. JavaScript and WebAssembly: These experimental features focus on improving the performance and capabilities of JavaScript and WebAssembly in Safari. Developers can utilize these features to create faster and more powerful web applications that can rival native software.

7. Web API Expansions: Safari’s experimental Web API features can expand the capabilities of web applications by offering new APIs for accessing device functionality, such as cameras, sensors, or location services. Enabling these features can unlock exciting possibilities for developers to create innovative web experiences.

8. Images, Video, and Audio Enhancements: Experimental features related to multimedia content can provide developers with access to advanced image and video processing capabilities, improved audio playback, and better integration of media elements on web pages. These features can enhance the viewing and listening experiences of users.

It’s important to note that enabling experimental features may come with potential risks, such as compatibility issues, performance limitations, or security vulnerabilities. Therefore, it is recommended to only activate these features if you are a developer or have a specific need for them. Regular users should avoid enabling experimental features to ensure a stable and secure browsing experience.

To enable or disable experimental features in Safari, navigate to Settings -> Safari -> Advanced -> Experimental Features. From there, you can toggle individual features on or off. If you encounter any issues or have specific queries, it’s always a good idea to reach out to Apple’s technical support for guidance.

Safari’s experimental WebKit features offer developers the opportunity to explore new web technologies and enhance their web applications. However, it is crucial to exercise caution when enabling these features, as they may come with potential drawbacks. Always weigh the benefits against the risks before activating any experimental features in Safari.

Do You Need Experimental WebKit Features On Your iPhone?

It is not necessary for the average iPhone user to enable experimental WebKit features. These features are typically designed for developers and advanced users who want to test new functionalities or provide feedback to Apple. Enabling experimental features may introduce instability or compatibility issues, and could potentially impact the performance and security of your device.

Here are a few reasons why you may not need experimental WebKit features on your iPhone:

1. Stability: Experimental features are still in the testing phase and may not be stable. They could potentially cause crashes or other issues while browsing the web.

2. Compatibility: Some experimental features may not be compatible with all websites or web applications. This means that certain websites may not function correctly or may not load at all.

3. Performance: Enabling experimental features may have a negative impact on your device’s performance, as they are not optimized for everyday use.

4. Security: Experimental features may have security vulnerabilities that could expose your device to potential risks. It is generally recommended to use stable and well-tested features to ensure a higher level of security.

Unless you are a developer or have specific reasons for enabling experimental WebKit features, it is generally best to stick with the stable and officially supported features of Safari on your iPhone.

What Does Experimental WebKit Features Mean?

Experimental WebKit features refer to new functionalities and capabilities that are being tested and developed by Apple within the Safari web browser. These features are not yet fully stable or officially released, but they are made available to developers for testing and experimentation purposes.

Key points about experimental WebKit features:

1. Purpose: These features are designed to provide developers with early access to new technologies and enhancements within Safari. They allow developers to explore and experiment with cutting-edge web capabilities before they are officially released.

2. Testing and feedback: By making these experimental features available, Apple encourages developers to test them and provide feedback. This feedback helps Apple identify and address any issues or bugs before the features are included in stable releases.

3. Developer-focused: Experimental WebKit features are primarily targeted towards developers who want to leverage the latest web technologies and stay ahead of the curve. They enable developers to build and optimize web experiences within their apps using the latest advancements in Safari.

4. Debugging and optimization: These features also provide tools and resources for developers to debug and optimize their web experiences. Developers can analyze performance, identify potential issues, and make necessary improvements to ensure their apps deliver the best possible user experience.

5. Limited stability: It’s important to note that experimental features may not be fully stable and could undergo significant changes or even be removed in future updates. They are intended for testing and evaluation purposes, and developers should be aware of the potential risks and limitations associated with using them.

Experimental WebKit features in Safari demonstrate Apple’s commitment to innovation and collaboration with developers. By providing early access to new web technologies, Apple empowers developers to create more advanced and immersive web experiences within their apps.

What Are All The Experimental WebKit Features On iPhone?

Here is a detailed list of experimental WebKit features available on iPhone:

1. Web Push on iOS and iPadOS: This feature allows websites to send push notifications to users even when they are not actively using the website. It provides a way for websites to engage with users and deliver timely updates or important information.

2. Improvements for Web Apps: WebKit introduces various enhancements to improve the performance and user experience of web applications on iPhone. These improvements include faster loading times, smoother animations, and better overall responsiveness.

3. Web Components: WebKit supports the use of Web Components, which are a set of web platform APIs that allow you to create reusable custom elements for your web applications. This feature promotes modularity and reusability, making it easier to develop and maintain complex web applications.

4. CSS Enhancements: WebKit includes experimental CSS features that provide developers with more flexibility and control over the visual styling of web pages. These features may include new layout options, advanced animations, or improved typography.

5. HTML Updates: WebKit introduces experimental HTML features that extend the capabilities of the HTML markup language. These updates may include new elements, attributes, or APIs that enable developers to create more interactive and dynamic web content.

6. JavaScript and WebAssembly: WebKit supports experimental JavaScript and WebAssembly features that enable developers to build high-performance web applications. These features may include new language features, optimizations, or APIs that improve the execution speed and efficiency of JavaScript and WebAssembly code.

7. Web API Enhancements: WebKit introduces experimental Web APIs that provide developers with additional functionality and access to device features. These APIs may include new sensor interfaces, storage options, or network protocols that enhance the capabilities of web applications on iPhone.

8. Images, Video, and Audio: WebKit includes experimental features related to handling and displaying images, videos, and audio on web pages. These features may include new image formats, video codecs, or audio enhancements that improve the quality and performance of multimedia content.

Please note that experimental WebKit features may not be fully supported or standardized yet, and their usage may require additional testing and caution. It is recommended to refer to the official WebKit documentation and guidelines for more information on using these features effectively.

How Do You Reset Experimental WebKit Features to Default Settings?

To reset experimental WebKit features to default settings, follow these steps:

1. Open the Settings app on your device. 2. Scroll down and tap on “Safari” to access Safari settings. 3. Within the Safari settings, scroll further down and tap on “Advanced.” 4. In the Advanced settings, look for “Experimental Features” and tap on it. 5. At the bottom of the Experimental Features page, you’ll find an option called “Reset All to Defaults.” Tap on it.

By performing these steps, you will reset all the experimental WebKit features to their default settings. It’s important to note that there won’t be a confirmation prompt, and the reset will take place immediately.

Please keep in mind that resetting experimental features will remove any customized settings or preferences you may have made. If you have specific experimental features enabled that you wish to keep, it’s advisable to note them down before performing the reset.

Experimental WebKit Features in Safari provide developers with the ability to debug and enhance web experiences within their apps. These features demonstrate Apple’s commitment to supporting developers and ensuring the best possible user experience. From web components to CSS, HTML, JavaScript, and WebAssembly, Safari’s Experimental Features offer a wide range of tools for developers to optimize and improve their web apps. Additionally, Safari 16.4 introduces Web Push on iOS and iPadOS, further enhancing the capabilities of web apps on Apple devices. However, it is important to note that these experimental features should only be enabled by developers or under the guidance of Apple technical support. For regular users, it is recommended to keep these features disabled to ensure a stable and secure browsing experience.

Related posts:

Sanjeev Singh

• Skip to main content
• Skip to search
• Skip to select language
• Sign up for free

-webkit-prefixed CSS extensions

User agents based on WebKit or Blink, such as Safari and Chrome, support several special extensions to CSS . These extensions are prefixed with -webkit- .

-webkit-prefixed properties without standard equivalents

Note: Avoid using on websites. These properties will only work in WebKit- or Blink-based browsers except where specified.

• -webkit-app-region
• -webkit-border-horizontal-spacing
• -webkit-border-vertical-spacing
• -webkit-box-reflect (supported with -webkit- by every browser, for compatibility reasons)
• -webkit-column-axis
• -webkit-column-progression
• -webkit-cursor-visibility
• -webkit-font-smoothing
• -webkit-hyphenate-limit-after
• -webkit-hyphenate-limit-before
• -webkit-hyphenate-limit-lines
• -webkit-line-align
• -webkit-line-box-contain
• -webkit-line-clamp
• -webkit-line-grid
• -webkit-line-snap
• -webkit-locale
• -webkit-logical-height
• -webkit-logical-width
• -webkit-margin-after
• -webkit-margin-before
• -webkit-mask-box-image-outset
• -webkit-mask-box-image-repeat
• -webkit-mask-box-image-slice
• -webkit-mask-box-image-source
• -webkit-mask-box-image-width
• -webkit-mask-box-image
• -webkit-mask-composite
• -webkit-mask-position-x (supported with -webkit- by every browser, for compatibility reasons)
• -webkit-mask-position-y (supported with -webkit- by every browser, for compatibility reasons)
• -webkit-mask-repeat-x (also supported without prefix)
• -webkit-mask-repeat-y (also supported without prefix)
• -webkit-mask-source-type
• -webkit-max-logical-height
• -webkit-max-logical-width
• -webkit-min-logical-height
• -webkit-min-logical-width
• -webkit-nbsp-mode
• -webkit-perspective-origin-x
• -webkit-perspective-origin-y
• -webkit-rtl-ordering
• -webkit-tap-highlight-color
• -webkit-text-decoration-skip
• -webkit-text-decorations-in-effect
• -webkit-text-fill-color
• -webkit-text-security
• -webkit-text-stroke-color
• -webkit-text-stroke-width
• -webkit-text-stroke
• -webkit-text-zoom
• -webkit-touch-callout
• -webkit-transform-origin-x
• -webkit-transform-origin-y
• -webkit-transform-origin-z
• -webkit-user-drag
• -webkit-user-modify

-webkit-prefixed properties with standard equivalents

Several old -webkit- prefixed properties have standard equivalents. Even if the name and syntax may be different, they shouldn't be used anymore at all.

For each of them, use the standard equivalent provided.

Use the standard border-block-end property instead.

Use the standard border-block-end-color property instead.

Use the standard border-block-end-style property instead.

Use the standard border-block-end-width property instead.

Use the standard border-block-start property instead.

Use the standard border-block-start-color property instead.

Use the standard border-block-start-style property instead.

Use the standard border-block-start-width property instead.

Use the standard border-inline-end property instead.

Use the standard border-inline-end-color property instead.

Use the standard border-inline-end-style property instead.

Use the standard border-inline-end-width property instead.

Use the standard border-inline-start property instead.

Use the standard border-inline-start-color property instead.

Use the standard border-inline-start-style property instead.

Use the standard border-inline-start-width property instead.

Use the CSS flexible box layout with the standard align-items property instead.

Use the CSS flexible box layout with the standard flex-direction property instead.

Use the CSS flexible box layout with the standard flex-basis , flex-grow , and flex-shrink properties instead.

Use the CSS flexible box layout with the standard flex-grow property instead.

Use the CSS flexible box layout with the standard flex-flow property instead.

Use the CSS flexible box layout with the standard order property instead.

Use the CSS flexible box layout with the standard justify-content property instead.

Use the CSS multicolumn layout with the standard break-after property instead.

Use the CSS multicolumn layout with the standard break-before property instead.

Use the CSS multicolumn layout with the standard break-inside property instead.

Use the standard hyphenate-character property instead.

Use the standard initial-letter property instead.

Use the standard margin-block-end property instead.

Use the standard margin-block-start property instead.

Use the standard padding-block-end property instead.

Use the standard padding-block-start property instead.

Use the standard padding-inline-end property instead.

Use the standard padding-inline-start property instead.

Pseudo-classes

• :-webkit-animating-full-screen-transition
• :-webkit-any()
• :-webkit-any-link *
• :-webkit-autofill
• :-webkit-autofill-strong-password
• :-webkit-drag
• :-webkit-full-page-media
• :-webkit-full-screen *
• :-webkit-full-screen-ancestor
• :-webkit-full-screen-document
• :-webkit-full-screen-controls-hidden

* Now standard.

Note: If there is an invalid pseudo-class within in a chain or group of selectors, the whole selector list is invalid.

Pseudo-elements

For web-compatibility reasons, Blink, WebKit, and Gecko browsers treat all pseudo-elements starting with ::-webkit- as valid.

• ::-webkit-file-upload-button *
• ::-webkit-inner-spin-button
• ::-webkit-input-placeholder
• ::-webkit-meter-bar
• ::-webkit-meter-even-less-good-value
• ::-webkit-meter-inner-element
• ::-webkit-meter-optimum-value
• ::-webkit-meter-suboptimum-value
• ::-webkit-progress-bar
• ::-webkit-progress-inner-element
• ::-webkit-progress-value
• ::-webkit-search-cancel-button
• ::-webkit-search-results-button
• ::-webkit-slider-runnable-track
• ::-webkit-slider-thumb

Note: Generally, if there is an invalid pseudo-element or pseudo-class within in a chain or group of selectors, the whole selector list is invalid. If a pseudo-element (but not pseudo-class) has a -webkit- prefix, As of Firefox 63, Blink, WebKit and Gecko browsers assume it is valid, not invalidating the selector list.

Media features

• -webkit-animation
• -webkit-device-pixel-ratio
• -webkit-transform-2d
• -webkit-transform-3d
• -webkit-transition
• Vendor Prefix glossary entry
• Mozilla vendor-prefixed CSS extensions
• Styling Form Controls on the WebKit Trac

Apple fixes Safari WebKit zero-day flaw exploited at Pwn2Own

Sergiu gatlan.

• May 14, 2024

Apple has released security updates to fix a zero-day vulnerability in the Safari web browser exploited during this year's Pwn2Own Vancouver hacking competition.

The company addressed the security flaw (tracked as CVE-2024-27834) on systems running macOS Monterey and macOS Ventura with improved checks.

While Apple only said that the vulnerability was reported by Manfred Paul, working with Trend Micro's Zero Day Initiative, this is one of the bugs the security researcher chained with an integer underflow bug to gain remote code execution (RCE) and earn $60,000 during Pwn2Own.

"An attacker with arbitrary read and write capability may be able to bypass Pointer Authentication," Apple explains in a Monday advisory.

Pointer authentication codes (PACs) are used on the arm64e architecture to detect and guard against unexpected changes to pointers in memory, with the CPU triggering app crashes following memory corruption events linked to authentication failures.

While Safari 17.5 is also available for iOS 17.5, iPadOS 17.5, macOS Sonoma 14.5, and visionOS 1.2, Apple has yet to confirm if it also patched the CVE-2024-27834 bug on these platforms.

If you run macOS Ventura or macOS Monterey, you can update Safari without updating macOS by going to  > System Settings > General > Software Update and clicking "More info…" under "Updates Available."

Pwn2Own Vancouver 2024

Security researchers collected $1,132,500 after exploiting and reporting 29 zero-days at this year's Vancouver hacking contest.

Manfred Paul emerged as the winner and earned $202,500 in cash after demoing an RCE zero-day combo against Apple's Safari web browser and a double-tap RCE exploit targeting an Improper Validation of Specified Quantity in Input weakness in the Google Chrome and Microsoft Edge web browsers during the first day of the hacking competition.

On the second day, Manfred Paul exploited an out-of-bounds (OOB) write zero-day bug to gain RCE and escaped Mozilla Firefox's sandbox via an exposed dangerous function weakness.

Google and Mozilla fixed the zero-days exploited at Pwn2Own Vancouver 2024 within days after the contest ended, with Google releasing patches five days later and Mozilla after just one day .

However, vendors rarely hurry to fix security flaws exploited at Pwn2Own since Trend Micro's Zero Day Initiative publicly discloses bug details after 90 days.

On Monday, Apple also backported security patches released in March to older iPhones and iPads, fixing an iOS zero-day tagged as exploited in attacks.

Related Articles:

Apple backports fix for zero-day exploited in attacks to older iPhones

Google fixes third actively exploited Chrome zero-day in a week

Apple blocked $7 billion in fraudulent App Store purchases in 4 years

PoC exploit released for RCE zero-day in D-Link EXO AX4800 routers

Microsoft fixes Windows zero-day exploited in QakBot malware attacks

• Previous Article
• Next Article

Post a Comment Community Rules

You need to login in order to post a comment.

Not a member yet? Register Now

You may also like:

Microsoft to start enforcing Azure multi-factor authentication in July

Ransomware gang targets Windows admins via PuTTy, WinSCP malvertising

Help us understand the problem. What is going on with this comment?

• Abusive or Harmful
• Inappropriate content
• Strong language

Read our posting guidelinese to learn what content is prohibited.

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

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.

More From Forbes

Ios 17.5—apple issues update now warning to all iphone users.

• Share to Facebook
• Share to Twitter
• Share to Linkedin

Apple has issued iOS 17.5 along with a warning to update your iPhone as soon as possible. That’s because iOS 17.5 fixes 15 security vulnerabilities, some of which are serious.

Apple remains tight-lipped about exactly what is fixed in iOS 17.5, to ensure as many people as possible are able to upgrade their iPhones before attackers can get hold of the details.

Among the important flaws patched in iOS 17.5 are an issue in the Kernel at the heart of the iPhone operating system tracked as CVE-2024-27818, which could allow an attacker to execute code. Another issue fixed in iOS 17.5, in AppleAVD, could see an adversary able to execute arbitrary code with Kernel privileges if a user downloads an app, Apple said on its support page .

Apple has issued iOS 17.5 along with a warning to update your iPhone as soon as possible.

05/14 update below. This article was first published on 05/13.

Another significant bug squashed in iOS 17.5 is a vulnerability in Voice Control that could allow an attacker to elevate privileges. Meanwhile, CVE-2024-27834 is a flaw in WebKit, the engine that underpins the Safari browser, which could allow an attacker to bypass Pointer Authentication.

An issue in MarketplaceKit tracked as CVE-2024-27852 and reported by researchers at security outfit Mysk could see a maliciously crafted webpage able to distribute a script that tracks users on other webpages.

Ghost Of Tsushima Is Already Flooded With Negative Reviews On Steam

‘this is a big deal’—congress suddenly hurtling toward a ‘crucial’ crypto vote that could blow up the price of bitcoin, ethereum and xrp, netflix s best new overlooked action movie is a must watch.

Sean Wright, head of application security at Featurespace, calls the fixes issued in iOS 17.5 “a mixed bag.”

The worst is the kernel flaw, he says. “This could be chained with some of the other vulnerabilities to allow an attacker to gain full access to the device.”

POC for iOS 17.5 Kernel Flaw Will Soon Be Ready

One day after iOS 17.5 was issued, more is being unveiled about the security fixes. Notably, a security researcher Meysam who claims to have reported the kernel vulnerability has described in a post on X, formally Twitter, how he reported the flaw in iOS 17.4.1—the previous version of iOS 17. He plans to publish a proof of concept to demonstrate how it works “soon.”

While he is keen to point out that this is not an exploit—ie a direct method of exploiting the issue—it does make updating to iOS 17.5 especially crucial. The more attackers know about the flaw, the more likely it is they can use it in attacks.

Apple Issues iOS 16.7.8 To Fix Already-Exploited Issue

Alongside iOS 17.5, Apple has issued iOS 16.7.8, fixing two issues, one of which is already being used in real-life attacks. Tracked as CVE-2024-23296, the flaw in RTKit could enable an attacker with arbitrary kernel read and write capability to bypass kernel memory protections. “Apple is aware of a report that this issue may have been exploited,” Apple wrote on its support page .

The iOS 16.7.8 is available for iPhone 8, iPhone 8 Plus, iPhone X, iPad 5th generation, iPad Pro 9.7-inch, and iPad Pro 12.9-inch 1st generation.

Why You Should Update Now To iOS 17.5 Or iOS 16.7.8

It’s been a while since Apple’s last security update, iOS 17.4.1 —released in March—which fixed multiple serious security flaws. The update before that, iOS 17.4, was an emergency patch for issues being used in real life attacks.

The iOS 16.7.8 update is similar as it also patches already-exploited security issues. If you have an older device, updating to iOS 16.7.8 is a no-brainer, given that the flaw is being used in attacks.

While iOS 17.5 doesn’t cover any already-exploited flaws—at least that we know about—some of the issues are serious making it important you update your iPhone as soon as you can.

At the same time, the iOS 17.5 update contains cool new features, including unwanted tracker protection, as well as bug fixes.

The iOS 17.5 update is available for the iPhone XS and later, iPad Pro 12.9-inch 2nd generation and later, iPad Pro 10.5-inch, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 6th generation and later and iPad mini 5th generation and later.

Two days after iOS 17.5 was released, some users are complaining about a Photos bug that is seeing deleted photos from years ago reappearing on people’s iPhones. This bug is certainly concerning, but it’s likely it will be fixed soon by Apple. I haven’t had any issues since updating to iOS 17.5.

If you care about your security, you will need to apply iOS 17.5 or iOS 16.7.8 manually, because Apple’s automatic updates can take a while to reach iPhones. It’s during this time that your device remains open to attack.

Wright says there is no need to panic, but ensure that you update “as soon as you can.”

So what are you waiting for? Go to your iPhone’s Settings > General > Software Update and download and install iOS 17.5 or iOS 16.7.8 now.

05/14 update: As well as important security fixes, the iOS 17.5 update contains a feature that helps stop unwanted tracking across platforms. Building on Apple’s iPhone feature to detect AirTags that might have been slipped into a bag or placed in a vehicle, the unwanted tracking tool in iOS 17.5 is a result of a partnership between Apple and its rival Google.

After releasing iOS 17.5, Apple has issued a press release to confirm the anti-tracking features are live. It describes how Apple and Google worked together to create an industry specification—Detecting Unwanted Location Trackers—for Bluetooth tracking devices. “This will help mitigate the misuse of devices designed to help keep track of belongings,” the statement reads, adding that Apple is implementing this capability in iOS 17.5, and Google in its Android 6.0+ devices.

The iOS 17.5 feature means users will get an “[Item] Found Moving With You” alert if an unknown Bluetooth tracking device is detected.

It works across platforms, with Bluetooth tag manufacturers including Chipolo, eufy, Jio, Motorola and Pebblebee saying future tags will be compatible.

Among the benefits, it offers instructions and best practices for manufacturers, “should they choose to build unwanted tracking alert capabilities into their products,” according to Apple and Google.

The standard is ongoing: Apple and Google are working with the Internet Engineering Task Force via the Detecting Unwanted Location Trackers working group to develop the official standard.

Update 05/15: Article updated to include details about iOS 17.5 photos bug.

• Editorial Standards
• Reprints & Permissions

Join The Conversation

One Community. Many Voices. Create a free account to share your thoughts. 

Forbes Community Guidelines

Our community is about connecting people through open and thoughtful conversations. We want our readers to share their views and exchange ideas and facts in a safe space.

In order to do so, please follow the posting rules in our site's  Terms of Service.   We've summarized some of those key rules below. Simply put, keep it civil.

Your post will be rejected if we notice that it seems to contain:

• False or intentionally out-of-context or misleading information
• Insults, profanity, incoherent, obscene or inflammatory language or threats of any kind
• Attacks on the identity of other commenters or the article's author
• Content that otherwise violates our site's  terms.

User accounts will be blocked if we notice or believe that users are engaged in:

• Continuous attempts to re-post comments that have been previously moderated/rejected
• Racist, sexist, homophobic or other discriminatory comments
• Attempts or tactics that put the site security at risk
• Actions that otherwise violate our site's  terms.

So, how can you be a power user?

• Stay on topic and share your insights
• Feel free to be clear and thoughtful to get your point across
• ‘Like’ or ‘Dislike’ to show your point of view.
• Protect your community.
• Use the report tool to alert us when someone breaks the rules.

Thanks for reading our community guidelines. Please read the full list of posting rules found in our site's  Terms of Service.

Special Features

Vendor voice.

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."

Samsung takes bite out of Apple over its mega marketing misstep

• Aghast iOS users report long-deleted photos back from the dead after update

Google, Apple gear to raise tracking tag stalker alarm

As one apple store votes against forming union, another may go on strike.

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. ®

• European Commission
• European Union
• Web Browser

Narrower topics

• Czech Republic
• Internet Explorer
• Microsoft Edge
• Netherlands

Broader topics

• Steve Wozniak

Send us news

Other stories you might like

You ok, apple seriously, your silicon lineup is … a mess, add ai servers to the list of idevices apple silicon could soon power, easing the cloud migration journey.

Apple broke the law with anti-union tactics in NYC, labor watchdog barks

Apple unveils m4 chip with neural engine capable of 38 tops, and some other kit, vivaldi composes split view sonata for browser on ipados, meta, spotify break apple's device fingerprinting rules – new claim, apple crushes creativity and its reputation in new ipad ad, apple on track for quarter of all iphones to be made in india by 2028.

• Advertise with us

Our Websites

• The Next Platform
• Blocks and Files

Your Privacy

• Cookies Policy
• Privacy Policy
• Ts & Cs

Copyright. All rights reserved © 1998–2024

• 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

Testing of iOS Browsers With Third-Party Engines Geofenced to EU

Developers who want to develop browsers for iOS with third-party engines can only test their apps on devices physically located in the EU, according to The Register .

Under the Digital Markets Act (DMA), Apple was designated as a gatekeeper in the European Union, compelling the company to make changes to its policies. With the release of iOS 17.4 , Apple began allowing the use of alternative browser engines within the EU . However, it has now emerged that testing of browsers with third-party engines is strictly geofenced to the EU, potentially hindering the ability of developers around the world to address security issues or implement updates efficiently.

The requirements raise some practical concerns about the feasibility of supporting a separate EU browser. Some developers have pointed out that Apple's extensive list of conditions makes it challenging to comply while also ensuring that the browser remains competitive and secure.

The European Commission has launched an investigation into Apple's compliance with the DMA, focusing on the restrictive nature of its latest changes. The investigation seeks to determine whether Apple's requirements are designed to circumvent the spirit of the DMA by making it difficult for competitors to operate on a level playing field.

Get weekly top MacRumors stories in your inbox.

Top Rated Comments

Good, if the EU wants to force this gatekeeper crap then development and testing should happen in the EU. Play stupid games....

I've been a fierce defender of the way Apple has done business. There's a reason iOS has been a secure (mostly) and malware-free platform. But man. The petty decisions there's making around the EU regulations sort of have soured me on that idea. Hard to defend these juvenile actions.

Popular Stories

Troubling iOS 17.5 Bug Reportedly Resurfacing Old Deleted Photos

iMessage Down for Some Users [Update: Service Restored]

Apple Previews Three New CarPlay Features Coming With iOS 18

Hands-On With the New M4 OLED iPad Pro

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

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

2 days ago by Tim Hardwick

3 days ago by Tim Hardwick

5 days ago by Juli Clover

5 days ago by Tim Hardwick

Things to Do in Monino, Russia - Monino Attractions

Things to do in monino.

• 5.0 of 5 bubbles
• Good for Kids
• Budget-friendly
• Hidden Gems
• Good for Big Groups
• Adventurous
• Good for a Rainy Day
• Good for Couples
• Honeymoon spot
• Good for Adrenaline Seekers
• Things to do ranked using Tripadvisor data including reviews, ratings, photos, and popularity.

1. The Central Air Force Museum

2. Church of St. George

Time in Elektrostal , Moscow Oblast, Russia now

• Tokyo 03:30PM
• Beijing 02:30PM
• Kyiv 09:30AM
• Paris 08:30AM
• London 07:30AM
• New York 02:30AM
• Los Angeles 11:30PM

Time zone info for Elektrostal

• The time in Elektrostal is 8 hours ahead of the time in New York when New York is on standard time, and 7 hours ahead of the time in New York when New York is on daylight saving time.
• Elektrostal does not change between summer time and winter time.
• The IANA time zone identifier for Elektrostal is Europe/Moscow.

Time difference from Elektrostal

Sunrise, sunset, day length and solar time for elektrostal.

• Sunrise: 04:04AM
• Sunset: 08:41PM
• Day length: 16h 37m
• Solar noon: 12:23PM
• The current local time in Elektrostal is 23 minutes ahead of apparent solar time.

Elektrostal on the map

• Location: Moscow Oblast, Russia
• Latitude: 55.79. Longitude: 38.46
• Population: 144,000

Best restaurants in Elektrostal

• #1 Tolsty medved - Steakhouses food
• #2 Ermitazh - European and japanese food
• #3 Pechka - European and french food

Find best places to eat in Elektrostal

• Best pubs & bars in Elektrostal
• Best steak restaurants in Elektrostal
• Best bbqs in Elektrostal

The 50 largest cities in Russia

• Yekaterinburg
• Novosibirsk
• Vladivostok

• Tours to Russia
• Practicalities
• Russia in Lists

Rusmania • Deep into Russia

Out of the Centre

Savvino-storozhevsky monastery and museum.

Zvenigorod's most famous sight is the Savvino-Storozhevsky Monastery, which was founded in 1398 by the monk Savva from the Troitse-Sergieva Lavra, at the invitation and with the support of Prince Yury Dmitrievich of Zvenigorod. Savva was later canonised as St Sabbas (Savva) of Storozhev. The monastery late flourished under the reign of Tsar Alexis, who chose the monastery as his family church and often went on pilgrimage there and made lots of donations to it. Most of the monastery’s buildings date from this time. The monastery is heavily fortified with thick walls and six towers, the most impressive of which is the Krasny Tower which also serves as the eastern entrance. The monastery was closed in 1918 and only reopened in 1995. In 1998 Patriarch Alexius II took part in a service to return the relics of St Sabbas to the monastery. Today the monastery has the status of a stauropegic monastery, which is second in status to a lavra. In addition to being a working monastery, it also holds the Zvenigorod Historical, Architectural and Art Museum.

Belfry and Neighbouring Churches

Located near the main entrance is the monastery's belfry which is perhaps the calling card of the monastery due to its uniqueness. It was built in the 1650s and the St Sergius of Radonezh’s Church was opened on the middle tier in the mid-17th century, although it was originally dedicated to the Trinity. The belfry's 35-tonne Great Bladgovestny Bell fell in 1941 and was only restored and returned in 2003. Attached to the belfry is a large refectory and the Transfiguration Church, both of which were built on the orders of Tsar Alexis in the 1650s.  

To the left of the belfry is another, smaller, refectory which is attached to the Trinity Gate-Church, which was also constructed in the 1650s on the orders of Tsar Alexis who made it his own family church. The church is elaborately decorated with colourful trims and underneath the archway is a beautiful 19th century fresco.

Nativity of Virgin Mary Cathedral

The Nativity of Virgin Mary Cathedral is the oldest building in the monastery and among the oldest buildings in the Moscow Region. It was built between 1404 and 1405 during the lifetime of St Sabbas and using the funds of Prince Yury of Zvenigorod. The white-stone cathedral is a standard four-pillar design with a single golden dome. After the death of St Sabbas he was interred in the cathedral and a new altar dedicated to him was added.

Under the reign of Tsar Alexis the cathedral was decorated with frescoes by Stepan Ryazanets, some of which remain today. Tsar Alexis also presented the cathedral with a five-tier iconostasis, the top row of icons have been preserved.

Tsaritsa's Chambers

The Nativity of Virgin Mary Cathedral is located between the Tsaritsa's Chambers of the left and the Palace of Tsar Alexis on the right. The Tsaritsa's Chambers were built in the mid-17th century for the wife of Tsar Alexey - Tsaritsa Maria Ilinichna Miloskavskaya. The design of the building is influenced by the ancient Russian architectural style. Is prettier than the Tsar's chambers opposite, being red in colour with elaborately decorated window frames and entrance.

At present the Tsaritsa's Chambers houses the Zvenigorod Historical, Architectural and Art Museum. Among its displays is an accurate recreation of the interior of a noble lady's chambers including furniture, decorations and a decorated tiled oven, and an exhibition on the history of Zvenigorod and the monastery.

Palace of Tsar Alexis

The Palace of Tsar Alexis was built in the 1650s and is now one of the best surviving examples of non-religious architecture of that era. It was built especially for Tsar Alexis who often visited the monastery on religious pilgrimages. Its most striking feature is its pretty row of nine chimney spouts which resemble towers.

Plan your next trip to Russia

Ready-to-book tours.

Your holiday in Russia starts here. Choose and book your tour to Russia.

REQUEST A CUSTOMISED TRIP

Looking for something unique? Create the trip of your dreams with the help of our experts.