webkit in safari

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 macos port.

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 debug build with debugging symbols and assertions:

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

Using Xcode

You can open WebKit.xcworkspace to build and debug WebKit within Xcode.

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.

Embedded Builds

iOS, tvOS and watchOS are all considered embedded builds. The first time after you install a new Xcode, you will need to run:

Without this step, you will see the error message: " target specifies product type ‘com.apple.product-type.tool’, but there’s no such product type for the ‘iphonesimulator’ platform. " when building target JSCLLIntOffsetsExtractor of project JavaScriptCore .

Run the following command to build a debug build with debugging symbols and assertions for embedded simulators:

or embedded devices:

where platform is ios , tvos or watchos .

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 991

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.

• Web Browser
• Google Chrome Browser
• Mozilla Firefox Browser
• Microsoft Edge Browser
• Apple Safari Browser
• Tor Browser
• Opera Browser
• DuckDuckGo Browser
• Brave Browser
• Layer Tab in Apple Safari Browser
• Console Tab in Safari Browser
• How to enable or disable iCloud Tabs in Safari for Mac/iOS?
• How to enable or disable content blockers in Safari?
• Audit Tab in Apple Safari Browser
• Graphics Tab in Apple Safari Browser
• How to block online tracking and ads in a Web Browser?
• How to change the default search engine in Browsers?
• How to Customize the Toolbar in Firefox?
• Customize Browser Interface and Font Sizes for Better Readability
• Keyboard Shortcuts for all Web Browser
• Best browser for Security and Privacy
• What is Browser Sandboxing?
• What are the privacy features of Brave browser?
• What are browser vulnerabilities and how to stay protected?
• What are the best internet browsers for 2024?
• Accessibility Features for Visually Impaired Users in Web Browsers
• Developer Resources Tool in Microsoft Edge Browser

New WebKit Features in Apple Safari 15.4

Discover the latest in web browsing with Safari 15.4!, a recent update for Apple devices, that packs exciting new features within WebKit. Expect smoother experiences, better visuals, and tighter security. Get ready for websites that feel faster, look incredible, and keep you safer than ever.

WebKit is like the powerful engine inside Safari that helps websites run smoothly. With this new update, the WebKit engine gets some upgrades to make it even better!

Table of Content

What is WebKit in Safari?

What’s new in safari 15.4, why care as a beginner web enthusiast.

WebKit is a powerful technology engine that lives inside the Safari web browser. Think of it like this:

• The Translator: WebKit understands the languages of the web (HTML, CSS, and JavaScript) and translates them into the visual websites and apps you see on your screen.
• The Taskmaster: It handles behind-the-scenes work like loading images, playing videos, and making those interactive forms function properly.
• The Rule Enforcer: WebKit maintains a set of rules for how websites are structured and how they communicate with the internet, keeping your browsing experience safe and secure.

Apple built Safari on top of WebKit, and every improvement brought to WebKit by developers translates into new features and enhancements for the Safari browser itself. This means new capabilities for web designers, better-looking websites, and a safer browsing experience for you.

1. Enhanced CSS Styling with the appearance Property:

Websites strive to make buttons, sliders, and checkboxes not just functional but visually appealing and in sync with your device’s style. Think about how these elements look consistent on your iPhone or Mac! The new appearance property is like handing developers a toolbox for tailoring how such webpage building blocks look without reinventing the wheel from scratch. This results in better visual consistency for you!

2. Beefed-Up Security with Content Security Policy (CSP):

Online security is a serious matter. WebKit’s latest Content Security Policy upgrade acts like a set of strict protocols (or rules) for how websites manage the data they load. These improvements aim to keep your information (like passwords and banking details) safe from potential bad actors lurking online. It’s all about minimizing your risks as you browse.

3. Flexible Measurement Mixing for Developers:

Imagine building a house you’ll need a mix of measurements, both big and small! Now, picture web developers facing a similar task when making websites look pixel-perfect across screens of all sizes.

Safari 15.4 allows them to cleverly combine traditional CSS units (like pixels, inches) with relative units (like percentages) using special mathematical functions. This translates to websites adapting brilliantly to your iPad, MacBook, or any device you use.

Bonus Features:

• mask: Website elements can now don creative masks with interesting shapes. This opens up opportunities for more playful designs.
• backface-visibility: It’s like hiding objects behind the main stage during a play. With this property, developers can temporarily tuck away webpage elements until they’re needed, boosting performance.
• text-combine-upright: Special formatting effects become possible for languages like Chinese, Japanese, and Korean that can arrange text vertically.

As you continue on your website-building journey, knowing about these new features puts you ahead of the curve:

• Seamless Experiences: WebKit enhancements will gradually make websites you visit appear even better across various Apple devices.
• Increased Security: Your browsing experience becomes inherently safer thanks to tighter restrictions placed on how websites operate behind the scenes.
• Endless Possibilities: These new tools empower developers to build more visually delightful and feature-rich websites than ever before!

Keep in mind, technology continues to evolve! Each Safari update may introduce even more thrilling WebKit features for crafting the websites of tomorrow. Stay curious and continue exploring this exciting area of web development.

Safari 15.4’s WebKit enhancements empower developers to create more visually stunning, secure, and user-friendly websites. From enhanced CSS styling capabilities to advanced security protocols, these updates make for a better browsing experience on your Apple devices.

Please Login to comment...

Similar reads.

• Apple Safari
• Web Browsers
• Otter.ai vs. Fireflies.ai: Which AI Transcribes Meetings More Accurately?
• Google Chrome Will Soon Let You Talk to Gemini In The Address Bar
• AI Interior Designer vs. Virtual Home Decorator: Which AI Can Transform Your Home Into a Pinterest Dream Faster?
• Top 10 Free Webclipper on Chrome Browser in 2024
• 30 OOPs Interview Questions and Answers (2024)

Improve your Coding Skills with Practice

What kind of Experience do you want to share?

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]

Apple details how superfast Safari upgrades help developers make web apps bigger and faster than ever before

Safari is now faster than ever.

Apple might have finally agreed to allow things like game streaming apps into the App Store but there are still plenty of apps that are only available via web-based alternatives in Safari. Those apps need to be bigger and faster than ever before and making that possible means being at the forefront of web-based technology and performance. Safari has historically been pretty quick, especially on the iPhone, and now the team behind it has detailed some recent speed improvements.

Safari is based on the WebKit web browser engine and it's the WebKit team that has detailed some changes that have been made to the underlying technology to enable web developers to build the kinds of experiences that they wouldn't normally be able to do.

Specifically, the Apple WebKit team says that it has been able to improve performance by around 60% of late, although it did take multiple different updates to the Safari app over the course of months in order to make that happen. Regardless, the upshot is the same — Safari is now faster than ever, and that's good news for developers and users alike.

Faster than fast

According to the blog post on the WebKit website, the speed improvements were made thanks to the introduction of the Speedometer 3.0 benchmarking system which in turn allowed WebKit developers to get a better understanding of how its software performs.

Discussing the tool, the WebKit team said that "these tooling improvements allowed us to quickly identify bottlenecks" with those bottlenecks then giving the team something to aim for.

The blog post then continued to detail what Apple was able to do including building a "shared understanding of web performance so that improvements can be made to enhance the user experience."

So how successful was it? As it turns out, pretty successful. "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," the post explains. "Even though individual progressions were often less than 1%, over time, they all stacked up together to make a big difference." The post continued, adding that the team is " 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."

Master your iPhone in minutes

iMore offers spot-on advice and guidance from our team of experts, with decades of Apple device experience to lean on. Learn more with iMore!

It's important to note that the improvements to performance when using Speedometer 3.0 don't just mean a better score for those running the tests, but rather real-world improvements that users of web apps across the world — and across Apple's platforms — can expect to be of benefit when running real apps.

It's also worth noting that outside the EU, all web browsers available for download via the best iPhone and iPad App Stores use the same WebKit browser engine at their core. That should ensure that these speed improvements will also benefit those who use other browsers on their devices, no matter which company makes them.

More from iMore

• How to manage privacy and security settings in Safari on iPhone and iPad
• This quick iPhone Safari trick will help you close all tabs and master Apple's mobile browser
• How to use tabs and private browsing in Safari for iPhone and iPad

Oliver Haslam has written about Apple and the wider technology business for more than a decade with bylines on How-To Geek, PC Mag, iDownloadBlog, and many more. He has also been published in print for Macworld, including cover stories. At iMore, Oliver is involved in daily news coverage and, not being short of opinions, has been known to 'explain' those thoughts in more detail, too. Having grown up using PCs and spending far too much money on graphics card and flashy RAM, Oliver switched to the Mac with a G5 iMac and hasn't looked back. Since then he's seen the growth of the smartphone world, backed by iPhone, and new product categories come and go. Current expertise includes iOS, macOS, streaming services, and pretty much anything that has a battery or plugs into a wall. Oliver also covers mobile gaming for iMore, with Apple Arcade a particular focus. He's been gaming since the Atari 2600 days and still struggles to comprehend the fact he can play console quality titles on his pocket computer.

Delta iPhone emulator also works on Mac and Apple Vision Pro — but you'll need a controller for the best experience

iPhone 17: Everything you need to know

Emulators on iPhone: Everything you need to know

Most Popular

• 2 Refurbished Apple Watch Ultra 2 smartwatches have started their international Apple Store rollout with 15% savings
• 3 iPad Air 6 to get the iPad Pro's mini-LED display in shock late leak — OLED iPad Pro won't be the only display boost in May
• 4 How to play games on Delta Game Emulator for iPhone — get to grips with the app everyone's talking about
• 5 iPhone and iPad owners can now AirPlay content, music, and even games to TVs in these hotels

• Skip to main content
• Skip to search
• Skip to select language
• Sign up for free
• English (US)

-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