Why should we add webkit before CSS3 attributes?-CSS Tutorial-php.cn

Home

Web Front-end

CSS Tutorial

Why should we add webkit before CSS3 attributes?

WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB

Dec 16, 2021 pm 03:43 PM

css

Because CSS needs to be compatible with the attribute support of different browsers, browser manufacturers will add a private prefix before the attribute to support new attributes; attributes with the prefix "-webkit-" can be used in webkit-based Normally used in browsers such as "safari" and "chrome" browsers.

Why should we add webkit before CSS3 attributes?

The operating environment of this tutorial: Windows 10 system, CSS3&&HTML5 version, Dell G3 computer.

Why should we add webkit before Css3 attributes

There are some new attributes in CSS3, such as box-reduis, box-orient, text- overflow, etc., these attributes did not exist or were not supported in previous versions. Therefore, for different browsers, their kernel names are specified so that they can parse these new attributes. This seems to be a reasonable explanation, that is, -moz- is for firefox, and -webkit- is for safari and chrome.

-moz represents the private properties of the firefox browser
-ms represents the private properties of the ie browser
-webkit represents safari and chrome private properties

Before the standard was determined, some browsers had already implemented some functions according to the initial draft in order to be compatible with the standards that were later determined. , so each browser uses its own private prefix to distinguish it from the standard. When the standard is established, major browsers will gradually support new CSS3 attributes without prefixes.

The example is as follows:

<html>
<head>
<style> 
div
{
width:300px;
height:100px;
background-color:#ff9900;
-moz-box-shadow: 10px 10px 5px #888888; /* 老的 Firefox */
box-shadow: 10px 10px 5px #888888;
}
</style>
</head>
<body>
<div></div>
</body>
</html>

Why do we need a private prefix? Because the W3C, the organization that formulates HTML and CSS standards, is very slow. Usually, a member of the w3c organization proposes a new attribute, such as rounded border-radius, and everyone thinks it is good, but w3c will not set a standard for this attribute, but will go through a very complicated process and go through a lot of reviews.

Browser vendors are not willing to wait that long. If they feel that an attribute is mature enough, they will add support to the browser. But to avoid changes when w3c announces the standard in the future, a private prefix will be added, such as -webkit-border-radius, to support new attributes in advance. When w3c announces the standard in the future, the standard writing method of border-radius is established. , and let the new version of the browser support the border-radius writing method.

For example, Chrome 10 does not recognize border-radius and can only use webkit-border-radius, but Chrome 12 can recognize it. So when writing CSS, writing like this can ensure that both Chrome10 and Chrome12 can display correctly when browsing web pages.

Currently there are many private prefixes that can no longer be written, but in order to be compatible with older versions of browsers, private prefixes and standard methods can still be used, and the transition will be gradual

(Learning video sharing: css video tutorial)

The above is the detailed content of Why should we add webkit before CSS3 attributes?. For more information, please follow other related articles on the PHP Chinese website!

Statement

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

Weekly Platform News: Web Apps in Galaxy Store, Tappable Stories, CSS SubgridApr 14, 2025 am 11:20 AM

In this week's roundup: Firefox gains locksmith-like powers, Samsung's Galaxy Store starts supporting Progressive Web Apps, CSS Subgrid is shipping in Firefox

Weekly Platform News: Internet Explorer Mode, Speed Report in Search Console, Restricting Notification PromptsApr 14, 2025 am 11:15 AM

In this week's roundup: Internet Explorer finds its way into Edge, Google Search Console touts a new speed report, and Firefox gives Facebook's notification

The Power (and Fun) of Scope with CSS Custom PropertiesApr 14, 2025 am 11:11 AM

You’re probably already at least a little familiar with CSS variables. If not, here’s a two-second overview: they are really called custom properties, you set

We Are ProgrammersApr 14, 2025 am 11:04 AM

Building websites is programming. Writing HTML and CSS is programming. I am a programmer, and if you're here, reading CSS-Tricks, chances are you're a

How Do You Remove Unused CSS From a Site?Apr 14, 2025 am 10:59 AM

Here's what I'd like you to know upfront: this is a hard problem. If you've landed here because you're hoping to be pointed at a tool you can run that tells

An Introduction to the Picture-in-Picture Web APIApr 14, 2025 am 10:57 AM

Picture-in-Picture made its first appearance on the web in the Safari browser with the release of macOS Sierra in 2016. It made it possible for a user to pop

Ways to Organize and Prepare Images for a Blur-Up Effect Using GatsbyApr 14, 2025 am 10:56 AM

Gatsby does a great job processing and handling images. For example, it helps you save time with image optimization because you don’t have to manually

Oh Hey, Padding Percentage is Based on the Parent Element's WidthApr 14, 2025 am 10:55 AM

I learned something about percentage-based (%) padding today that I had totally wrong in my head! I always thought that percentage padding was based on the

See all articles