


Weekly Platform News: Focus Rings, Donut Scope, More em Units, and Global Privacy Control
Mar 26, 2025 am 10:33 AMThis week's web development news covers significant updates across various platforms. Key highlights include Chrome's handling of focus rings, the enhanced capabilities of the CSS :not()
selector, major adoption of Global Privacy Control (GPC), and a compelling argument for em-based media queries. We also explore a CSS solution to improve form validation styling.
Chrome's Focus Ring Behavior Changes
Chrome, Edge, and other Chromium-based browsers currently display focus rings on button clicks. This differs from Safari and Firefox, which only show focus rings when keyboard navigation is used. Developers have employed workarounds using data-whatintent
and :focus-visible
to manage this behavior. However, Chrome 90 will eliminate the need for these workarounds by changing its user agent stylesheet to prioritize :focus-visible
, thus suppressing focus rings on clicks and taps while preserving them for keyboard users.
Leveraging CSS :not()
for "Donut Scope" Selection
The A:not(B *)
selector pattern allows selecting all A
elements not descended from B
. Expanding this to A B:not(C *)
creates a "donut scope," enabling precise selection of elements within a specific context, excluding those within a nested element. For example, article p:not(blockquote *)
selects all paragraphs within an article, excluding those inside blockquotes.
Global Privacy Control Gains Traction
Global Privacy Control (GPC), a legally enforceable privacy signal using the Sec-GPC: 1
header, signals user preference against data sharing or sale. The New York Times is the first major publisher to fully support GPC, with others like The Washington Post and Automattic pledging support shortly. When a GPC signal is detected, compliant sites will cease sharing user data (excluding service providers) where relevant privacy laws apply.
The Advantages of em-Based Media Queries
Websites using pixel-based font sizes (font-size: 20px
) are unresponsive to browser-level font size adjustments. Using em
and rem
units allows responsiveness to user preferences. For consistent behavior, media queries should also use em
units (e.g., min-width: 80em
). This ensures responsive layouts adapt correctly even when users adjust their default font size, preventing issues like excessively short lines in multi-column layouts. A PostCSS plugin simplifies the conversion from px
to em
in media queries.
Improving Form Validation Styling with :user-invalid
The standard CSS :invalid
pseudo-class has limitations in form validation. It triggers on every keystroke and immediately on page load for required fields, potentially causing a confusing user experience. The :user-invalid
pseudo-class, already supported in Firefox as :-moz-ui-invalid
, addresses these issues by only applying after significant user interaction. Efforts are underway to standardize :user-invalid
across other browsers.
The above is the detailed content of Weekly Platform News: Focus Rings, Donut Scope, More em Units, and Global Privacy Control. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

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

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

CSS blocks page rendering because browsers view inline and external CSS as key resources by default, especially with imported stylesheets, header large amounts of inline CSS, and unoptimized media query styles. 1. Extract critical CSS and embed it into HTML; 2. Delay loading non-critical CSS through JavaScript; 3. Use media attributes to optimize loading such as print styles; 4. Compress and merge CSS to reduce requests. It is recommended to use tools to extract key CSS, combine rel="preload" asynchronous loading, and use media delayed loading reasonably to avoid excessive splitting and complex script control.

ThebestapproachforCSSdependsontheproject'sspecificneeds.Forlargerprojects,externalCSSisbetterduetomaintainabilityandreusability;forsmallerprojectsorsingle-pageapplications,internalCSSmightbemoresuitable.It'scrucialtobalanceprojectsize,performanceneed

No,CSSdoesnothavetobeinlowercase.However,usinglowercaseisrecommendedfor:1)Consistencyandreadability,2)Avoidingerrorsinrelatedtechnologies,3)Potentialperformancebenefits,and4)Improvedcollaborationwithinteams.

CSSismostlycase-insensitive,butURLsandfontfamilynamesarecase-sensitive.1)Propertiesandvalueslikecolor:red;arenotcase-sensitive.2)URLsmustmatchtheserver'scase,e.g.,/images/Logo.png.3)Fontfamilynameslike'OpenSans'mustbeexact.

Autoprefixer is a tool that automatically adds vendor prefixes to CSS attributes based on the target browser scope. 1. It solves the problem of manually maintaining prefixes with errors; 2. Work through the PostCSS plug-in form, parse CSS, analyze attributes that need to be prefixed, and generate code according to configuration; 3. The usage steps include installing plug-ins, setting browserslist, and enabling them in the build process; 4. Notes include not manually adding prefixes, keeping configuration updates, prefixes not all attributes, and it is recommended to use them with the preprocessor.

CSScounterscanautomaticallynumbersectionsandlists.1)Usecounter-resettoinitialize,counter-incrementtoincrease,andcounter()orcounters()todisplayvalues.2)CombinewithJavaScriptfordynamiccontenttoensureaccurateupdates.

In CSS, selector and attribute names are case-sensitive, while values, named colors, URLs, and custom attributes are case-sensitive. 1. The selector and attribute names are case-insensitive, such as background-color and background-Color are the same. 2. The hexadecimal color in the value is case-sensitive, but the named color is case-sensitive, such as red and Red is invalid. 3. URLs are case sensitive and may cause file loading problems. 4. Custom properties (variables) are case sensitive, and you need to pay attention to the consistency of case when using them.

CSSselectorsandpropertynamesarecase-insensitive,whilevaluescanbecase-sensitivedependingoncontext.1)Selectorslike'div'and'DIV'areequivalent.2)Propertiessuchas'background-color'and'BACKGROUND-COLOR'aretreatedthesame.3)Valueslikecolornamesarecase-insens
