
GITHUB . COM {
}
Detected CMS Systems:
- Wordpress (2 occurrences)
Title:
How to refer to the corner-shaped padding/border/content edges ยท Issue #5132 ยท w3c/csswg-drafts
Description:
Are the padding/border/content edges rectangular, and then border-radius / corner shaping gets applied, yielding the ???? (shaped padding/border/content edges ?), or are padding/border/content edges themselves modified by border-radius /...
Website Age:
17 years and 8 months (reg. 2007-10-09).
Matching Content Categories {๐}
- Social Networks
- Careers
- Technology & Computing
Content Management System {๐}
What CMS is github.com built with?
Github.com utilizes WORDPRESS.
Traffic Estimate {๐}
What is the average monthly size of github.com audience?
๐๐ Tremendous Traffic: 10M - 20M visitors per month
Based on our best estimate, this website will receive around 10,000,019 visitors per month in the current month.
However, some sources were not loaded, we suggest to reload the page to get complete results.
check SE Ranking
check Ahrefs
check Similarweb
check Ubersuggest
check Semrush
How Does Github.com Make Money? {๐ธ}
Subscription Packages {๐ณ}
We've located a dedicated page on github.com that might include details about subscription plans or recurring payments. We identified it based on the word pricing in one of its internal links. Below, you'll find additional estimates for its monthly recurring revenues.How Much Does Github.com Make? {๐ฐ}
Subscription Packages {๐ณ}
Prices on github.com are in US Dollars ($).
They range from $4.00/month to $21.00/month.
We estimate that the site has approximately 4,989,889 paying customers.
The estimated monthly recurring revenue (MRR) is $20,957,532.
The estimated annual recurring revenues (ARR) are $251,490,385.
Wordpress Themes and Plugins {๐จ}
What WordPress theme does this site use?
It is strange but we were not able to detect any theme on the page.
What WordPress plugins does this website use?
It is strange but we were not able to detect any plugins on the page.
Keywords {๐}
paddingbordercontent, edges, frivoal, edge, refer, cssbox, commented, shaped, work, sign, cornershaped, issue, backgrounds, terms, doesnt, cssbackgrounds, current, fantasai, projects, borderradius, corner, invoke, term, added, leaverou, member, cssmeetingbot, collaborator, navigation, pull, requests, actions, security, closed, rectangular, shaping, padding, specs, radius, find, suggest, terminology, effect, explicitly, addition, spec, add, cases, matter, depend,
Topics {โ๏ธ}
corner-shaped padding/border/content edges shaped padding/border/content edges padding/border/content edges rectangular unshaped padding/border/content edge padding/border/content edges org/css-box-4/ padding/border/content edge leaverou edits member css-box-4 shaped padding edge css working group specs work fantasai added border-radius / corner type projects existing ambiguous terms css-background-3 ๏ฟฝcontoured xxx edgeโ padding edge full irc log csswg possibly future specs resolution corner shaping corner-shaping shaped version gh issue adjusted border radius border-radius border-radius backgrounds-3 backgrounds-4 corner-shape edges //drafts shaped projects milestone terms cross-ref proposed change cross linking milestone relationships personal information reading https extra terminology effect explicitly explicitely depend bikeshed names spec defining
Payment Methods {๐}
- Braintree
Questions {โ}
- Already have an account?
- Are the padding/border/content edges rectangular, and then border-radius / corner shaping gets applied, yielding the ?
- Captured in the minutes, but not in the resolution: We're specifically looking for an adjective to qualify the "?
- Doesn't conflict with anything, so that's good, but it seems very generic, and it doesn't seem obvious to me: "adjusted in what way?
- How about โcontoured xxx edgeโ?
- In other words, when you want to refer to the shaped padding edge, do you just use cross-ref to padding edge, and let other specs work their magic to shape that appropriately, or do you have to refer to border radius and other kinds of corner shaping?
- Adjusted/unadjusted?
Schema {๐บ๏ธ}
DiscussionForumPosting:
context:https://schema.org
headline:How to refer to the corner-shaped padding/border/content edges
articleBody:Are the padding/border/content edges rectangular, and then border-radius / corner shaping gets applied, yielding the ???? (shaped padding/border/content edges ?), or are padding/border/content edges themselves modified by border-radius / corner?
In other words, when you want to refer to the shaped padding edge, do you just use cross-ref to padding edge, and let other specs work their magic to shape that appropriately, or do you have to refer to border radius and other kinds of corner shaping?
Reading https://drafts.csswg.org/css-box-4/, there's no mention of radius, corners, or shapes, so that would lead me to believe that the padding/border/content edge are rectangular, and if you want the shaped version, you have to invoke that yourself (or find some term that does that, but I couldn't find it).
On the other hand, https://www.w3.org/TR/css-backgrounds-4/#the-border-radius, seems to suggest that the padding/border/content edge themselves do get shaped, which would mean that you don't need to reach for extra terminology or invoke the effect explicitly.
In addition to being verbose, having to explicitly invoke the effect yourself means that any spec that wants to talk about these edges needs to take a dependency not just on backgrounds-3, but also backgrounds-4 to make sure corner-shape is accounted for as well, and possibly future specs if we add more things later.
I'd suggest that css-box-4 should introduce the terms `shaped padding/border/content edge` and `unshaped padding/border/content edge`, in addition to the existing ambiguous terms that can continue to be used in the cases where the difference doesn't matter. css-box-4 would explicitely depend on css-background-3 to take border-radius into account, but need not depend on backgrounds-4 for `corner-shaping`: backgrounds-4 can itself use that new terminology to say that it modifies it.
author:
url:https://github.com/frivoal
type:Person
name:frivoal
datePublished:2020-05-29T03:13:16.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:9
url:https://github.com/5132/csswg-drafts/issues/5132
context:https://schema.org
headline:How to refer to the corner-shaped padding/border/content edges
articleBody:Are the padding/border/content edges rectangular, and then border-radius / corner shaping gets applied, yielding the ???? (shaped padding/border/content edges ?), or are padding/border/content edges themselves modified by border-radius / corner?
In other words, when you want to refer to the shaped padding edge, do you just use cross-ref to padding edge, and let other specs work their magic to shape that appropriately, or do you have to refer to border radius and other kinds of corner shaping?
Reading https://drafts.csswg.org/css-box-4/, there's no mention of radius, corners, or shapes, so that would lead me to believe that the padding/border/content edge are rectangular, and if you want the shaped version, you have to invoke that yourself (or find some term that does that, but I couldn't find it).
On the other hand, https://www.w3.org/TR/css-backgrounds-4/#the-border-radius, seems to suggest that the padding/border/content edge themselves do get shaped, which would mean that you don't need to reach for extra terminology or invoke the effect explicitly.
In addition to being verbose, having to explicitly invoke the effect yourself means that any spec that wants to talk about these edges needs to take a dependency not just on backgrounds-3, but also backgrounds-4 to make sure corner-shape is accounted for as well, and possibly future specs if we add more things later.
I'd suggest that css-box-4 should introduce the terms `shaped padding/border/content edge` and `unshaped padding/border/content edge`, in addition to the existing ambiguous terms that can continue to be used in the cases where the difference doesn't matter. css-box-4 would explicitely depend on css-background-3 to take border-radius into account, but need not depend on backgrounds-4 for `corner-shaping`: backgrounds-4 can itself use that new terminology to say that it modifies it.
author:
url:https://github.com/frivoal
type:Person
name:frivoal
datePublished:2020-05-29T03:13:16.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:9
url:https://github.com/5132/csswg-drafts/issues/5132
Person:
url:https://github.com/frivoal
name:frivoal
url:https://github.com/frivoal
name:frivoal
InteractionCounter:
interactionType:https://schema.org/CommentAction
userInteractionCount:9
interactionType:https://schema.org/CommentAction
userInteractionCount:9
External Links {๐}(4)
Analytics and Tracking {๐}
- Site Verification - Google
Libraries {๐}
- Clipboard.js
- D3.js
- Lodash
Emails and Hosting {โ๏ธ}
Mail Servers:
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
Name Servers:
- dns1.p08.nsone.net
- dns2.p08.nsone.net
- dns3.p08.nsone.net
- dns4.p08.nsone.net
- ns-1283.awsdns-32.org
- ns-1707.awsdns-21.co.uk
- ns-421.awsdns-52.com
- ns-520.awsdns-01.net