Home Web Front-end CSS Tutorial Why Does the `:not()` Selector Behave Differently in Safari Compared to Chrome and Firefox?

Why Does the `:not()` Selector Behave Differently in Safari Compared to Chrome and Firefox?

Nov 27, 2024 am 09:03 AM

Why Does the `:not()` Selector Behave Differently in Safari Compared to Chrome and Firefox?

:not() Selector Discrepancy: Safari versus Chrome/Firefox

The :not() CSS selector, used to exclude specific elements from a selection, has been found to behave differently in Safari compared to Chrome and Firefox. This discrepancy has caused confusion for developers, prompting an investigation into its underlying cause.

According to recent observations, Safari now fully supports the level 4 specification of :not(), which allows for complex selectors in its arguments. This feature brings it into alignment with jQuery's implementation. However, Chrome and Firefox currently support only simple selectors as arguments for :not().

The :not() selector anomaly stems from the use of complex selectors within its parentheses. A complex selector comprises multiple simple selectors joined by combinators, such as descendant, adjacent sibling, and general sibling. In the provided code snippet, the selector p div represents a complex selector, as it combines two simple selectors (p and div) with a descendant combinator.

Since Chrome and Firefox do not support complex selectors for :not() arguments, the p div portion in the provided code is not recognized. As a result, the :not() selector is effectively ignored, and the fallback rule em:not(...) applies. This fallback rule, which specifies red as the color for all elements, is responsible for the red text observed in Chrome and Firefox.

Conversely, Safari, with its support for complex selectors in :not(), correctly excludes elements within

elements from the red color specification. This results in the blue text displayed in Safari.

At present, the timeline for when Chrome and Firefox will support complex selectors for :not() remains uncertain. However, the implementation of the level 4 specification in Safari is a significant development that aligns it with the latest web standards and provides enhanced functionality for CSS selectors.

The above is the detailed content of Why Does the `:not()` Selector Behave Differently in Safari Compared to Chrome and Firefox?. For more information, please follow other related articles on the PHP Chinese website!

Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Tools

Notepad++7.3.1

Notepad++7.3.1

Easy-to-use and free code editor

SublimeText3 Chinese version

SublimeText3 Chinese version

Chinese version, very easy to use

Zend Studio 13.0.1

Zend Studio 13.0.1

Powerful PHP integrated development environment

Dreamweaver CS6

Dreamweaver CS6

Visual web development tools

SublimeText3 Mac version

SublimeText3 Mac version

God-level code editing software (SublimeText3)

Vue 3 Vue 3 Apr 02, 2025 pm 06:32 PM

It's out! Congrats to the Vue team for getting it done, I know it was a massive effort and a long time coming. All new docs, as well.

Can you get valid CSS property values from the browser? Can you get valid CSS property values from the browser? Apr 02, 2025 pm 06:17 PM

I had someone write in with this very legit question. Lea just blogged about how you can get valid CSS properties themselves from the browser. That's like this.

A bit on ci/cd A bit on ci/cd Apr 02, 2025 pm 06:21 PM

I'd say "website" fits better than "mobile app" but I like this framing from Max Lynch:

Stacked Cards with Sticky Positioning and a Dash of Sass Stacked Cards with Sticky Positioning and a Dash of Sass Apr 03, 2025 am 10:30 AM

The other day, I spotted this particularly lovely bit from Corey Ginnivan’s website where a collection of cards stack on top of one another as you scroll.

Using Markdown and Localization in the WordPress Block Editor Using Markdown and Localization in the WordPress Block Editor Apr 02, 2025 am 04:27 AM

If we need to show documentation to the user directly in the WordPress editor, what is the best way to do it?

Comparing Browsers for Responsive Design Comparing Browsers for Responsive Design Apr 02, 2025 pm 06:25 PM

There are a number of these desktop apps where the goal is showing your site at different dimensions all at the same time. So you can, for example, be writing

How to Use CSS Grid for Sticky Headers and Footers How to Use CSS Grid for Sticky Headers and Footers Apr 02, 2025 pm 06:29 PM

CSS Grid is a collection of properties designed to make layout easier than it’s ever been. Like anything, there's a bit of a learning curve, but Grid is

Google Fonts   Variable Fonts Google Fonts Variable Fonts Apr 09, 2025 am 10:42 AM

I see Google Fonts rolled out a new design (Tweet). Compared to the last big redesign, this feels much more iterative. I can barely tell the difference

See all articles