The cleverness of the rounded corners of CSS borders is its flexible application. It can not only set a unified rounded corner radius, but also set different values ??for different corners. However, when the rounded radii overlap, the browser does some "behind the scenes" processing, which can lead to some unexpected results.
Many developers are familiar with the "999em hack" technique to create "pill-shaped" rectangles. By setting a huge border-radius value (such as 999em or 999vmax), the corners of the rectangle can be perfectly rounded into semicircles. The advantage of this method is that it can achieve the effect without knowing the size of the rectangle.
However, this technique may have abnormal behavior in some cases. For example, when we try to create a "pill-shaped" rounded corner on the right side of a rectangle and set a smaller rounded corner on the left, the rounded corner on the left may disappear or become extremely small.
This is because in order to prevent the overlap of rounded corner radii, the browser will adjust it according to the specification. The complex formulas in the specification are designed to ensure that all rounded radii are scaled down to scale, thus avoiding overlap.
The browser calculates the ratio of the sum of the length of each side of the rectangle to its adjacent rounded corner radius. It then multiplies all the rounded radii by the smallest of these ratios. This way, all rounded radii will be scaled down until it no longer overlaps.
Let's illustrate with an example: if the rectangle is 200px in width, 100px in height, the rounded corner radius on the right is 400px in radius on the left is 40px in radius. The browser calculates the ratio:
<code>頂部:200px / (40px 400px) = 0.455右側(cè):100px / (400px 400px) = 0.125底部:200px / (40px 400px) = 0.455左側(cè):100px / (40px 40px) = 1.25</code>
The minimum ratio is 0.125, so all rounded radii will be multiplied by 0.125. The result is that the radius of the rounded corner on the right becomes 50px and the radius of the rounded corner on the left becomes 5px.
This scale-down mechanism ensures that the rounded corner radii does not overlap, but at the same time it can also cause the smaller rounded corner radii to be over-shrinked and even appear to disappear.
The reason why the browser chooses this way is that it can maintain the proportional relationship between the radius of the rounded corners. If the browser adopts other strategies, such as narrowing the maximum rounded radius, it may cause the end result to be more different from the developer's expectations.
In short, understanding the processing mechanism of overlapping rounded corners in CSS borders helps developers better control the rounded corner effects and avoid unexpected results. Thanks to my colleague Catherine for first discovering this issue, and James helped me understand the specification!
The above is the detailed content of What Happens When Border Radii Overlap?. 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
