To put it simply, starting from CSS3, the CSS specification has been split into many modules (modules) for individual upgrades, or new requirements have been established and standardized as a new module. Therefore, there will no longer be so-called major version number changes such as CSS4 and CSS5 in the future, but only a certain module-level transition of CSS.
Before the introduction of modularity
According to the CSS working group, there is no concept of version in the history of CSS, only the concept of "level". For example, CSS3 is actually CSS Level 3, CSS2 is CSS Level 2, and CSS Level 1 is of course CSS1. Each level builds on the previous level.
Everyone knows that CSS1 has been obsolete a long time ago. CSS2 is actually basically obsolete. However, CSS1, CSS2 (and CSS2.1) were large and comprehensive specifications at the time. Moreover, when CSS2 became the final standard, the CR stage had not yet been defined in the W3C specification process.
Later, W3C further improved the specification development process, requiring each specification to go through the following five stages:
1. Working Draft
(WD, Working Draft)
2. Final working draft
(LC/LCWD, Last Call Working Draft)
3. Candidate recommendation
(CR, Candidate Recommendation)
4. Proposed recommendation
(PR, Proposed Recommendation)
5. Recommended standard
(REC, Recommendation)
Because the original CSS2 has not gone through the CR stage, so there are many problems. The CSS working group was overwhelmed with endless "bug fixes". As a result, they decided to make a revision of CSS2, which is CSS2.1 (CSS Level 2 Revision 1).
In other words, CSS2.1 is actually just a revised version of CSS2, with no substantial changes. Some content in CSS2 was considered immature by the CSS working group and was deleted from CSS2.1. These deleted contents are considered to be rolled back to the CR stage of the process - equivalent to the need for "rewinding". (Later, these contents were basically in the form of CSS modules, revised and supplemented, and entered CSS Level 3.)
CSS2.1 and previous CSS specifications wrote all the contents in one document. As CSS features become more and more complex, the CSS specification becomes longer and longer. The PDF version of CSS2.1 has 430 pages. This brings great inconvenience to errata and further upgrades. Because the upgrade progress of different parts of the document cannot be forced to be consistent.
So, the CSS working group decided to take the modular route starting from CSS2.1. That is to say, the content that needs to be upgraded is separated into independent modules, and new requirements are also established as new modules. Since then, CSS has entered Level 3.
After the introduction of modularity
After CSS adopts the modular route, there are three types of modules, and their naming methods are very noteworthy.
CSS Level 2 original modules: Selector, Color, Values and Units, BackgroundS and Borders, etc. These are all modules separated from the original CSS specification. The naming of these modules will start from Level 3 from the beginning, such as Selectors Level 3, CSS Backgrounds and Borders Level 3, because they all start on the basis of CSS Level 2.
New modules: Multi-column Layout, Transitions, Flexible Box, Transforms, etc. are all newly added modules. Similar features did not exist in CSS before. Therefore, their naming will start from Level 1, such as CSS Transitions Level 1 and CSS Flexible Box Module Level 1.
Of course, there are also things that CSS2.1 removed from CSS2. As mentioned before, "the content in CSS2 that was deleted by CSS2.1 is considered to have fallen back to the CR stage", and most of the content will be "reincarnated" in the form of CSS Level 3. Once they enter the CR stage, they will It will replace the previous corresponding content and become the new standard.
OK, the advancement of the specification of any of the above modules from WD to the REC stage either means the birth of a new CSS module or the rebirth of an old CSS module!
I hope the following picture can explain the naming of CSS modules more intuitively:
The above is the detailed content of Do you know why CSS3 will not be followed by CSS4?. For more information, please follow other related articles on the PHP Chinese website!

Linking CSS files to HTML can be achieved by using elements in part of HTML. 1) Use tags to link local CSS files. 2) Multiple CSS files can be implemented by adding multiple tags. 3) External CSS files use absolute URL links, such as. 4) Ensure the correct use of file paths and CSS file loading order, and optimize performance can use CSS preprocessor to merge files.

Choosing Flexbox or Grid depends on the layout requirements: 1) Flexbox is suitable for one-dimensional layouts, such as navigation bar; 2) Grid is suitable for two-dimensional layouts, such as magazine layouts. The two can be used in the project to improve the layout effect.

The best way to include CSS files is to use tags to introduce external CSS files in the HTML part. 1. Use tags to introduce external CSS files, such as. 2. For small adjustments, inline CSS can be used, but should be used with caution. 3. Large projects can use CSS preprocessors such as Sass or Less to import other CSS files through @import. 4. For performance, CSS files should be merged and CDN should be used, and compressed using tools such as CSSNano.

Yes,youshouldlearnbothFlexboxandGrid.1)Flexboxisidealforone-dimensional,flexiblelayoutslikenavigationmenus.2)Gridexcelsintwo-dimensional,complexdesignssuchasmagazinelayouts.3)Combiningbothenhanceslayoutflexibilityandresponsiveness,allowingforstructur

What does it look like to refactor your own code? John Rhea picks apart an old CSS animation he wrote and walks through the thought process of optimizing it.

CSSanimationsarenotinherentlyhardbutrequirepracticeandunderstandingofCSSpropertiesandtimingfunctions.1)Startwithsimpleanimationslikescalingabuttononhoverusingkeyframes.2)Useeasingfunctionslikecubic-bezierfornaturaleffects,suchasabounceanimation.3)For

@keyframesispopularduetoitsversatilityandpowerincreatingsmoothCSSanimations.Keytricksinclude:1)Definingsmoothtransitionsbetweenstates,2)Animatingmultiplepropertiessimultaneously,3)Usingvendorprefixesforbrowsercompatibility,4)CombiningwithJavaScriptfo

CSSCountersareusedtomanageautomaticnumberinginwebdesigns.1)Theycanbeusedfortablesofcontents,listitems,andcustomnumbering.2)Advancedusesincludenestednumberingsystems.3)Challengesincludebrowsercompatibilityandperformanceissues.4)Creativeusesinvolvecust


Hot AI Tools

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

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

Undress AI Tool
Undress images for free

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

Dreamweaver Mac version
Visual web development tools

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

EditPlus Chinese cracked version
Small size, syntax highlighting, does not support code prompt function

MinGW - Minimalist GNU for Windows
This project is in the process of being migrated to osdn.net/projects/mingw, you can continue to follow us there. MinGW: A native Windows port of the GNU Compiler Collection (GCC), freely distributable import libraries and header files for building native Windows applications; includes extensions to the MSVC runtime to support C99 functionality. All MinGW software can run on 64-bit Windows platforms.

SecLists
SecLists is the ultimate security tester's companion. It is a collection of various types of lists that are frequently used during security assessments, all in one place. SecLists helps make security testing more efficient and productive by conveniently providing all the lists a security tester might need. List types include usernames, passwords, URLs, fuzzing payloads, sensitive data patterns, web shells, and more. The tester can simply pull this repository onto a new test machine and he will have access to every type of list he needs.
