GITHUB . COM {}

Detected CMS Systems:

Wordpress (2 occurrences)

Analyzed Page
Matching Content Categories
CMS
Monthly Traffic Estimate
How Does Github.com Make Money
How Much Does Github.com Make
Wordpress Themes And Plugins
Keywords
Topics
Payment Methods
Questions
Schema
External Links
Analytics And Tracking
Libraries
Hosting Providers

We are analyzing https://github.com/w3c/csswg-drafts/issues/2282.

Title:
[css-pseudo] ::first-line and line-height · Issue #2282 · w3c/csswg-drafts
Description:
Specs: https://www.w3.org/TR/css-pseudo-4/#first-line-pseudo The part of the specs related to the issue raised: The ::first-line pseudo-element’s generated box behaves similar to that of an inline-level element, but with certain restrict...
Website Age:
17 years and 8 months (reg. 2007-10-09).

Matching Content Categories {📚}

Technology & Computing
Graphic Design
Social Networks

Content Management System {📝}

What CMS is github.com built with?

Github.com is built with 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 {🔍}

firstline, lineheight, line, inline, csspseudo, element, properties, block, apply, reduced, box, behave, root, fantasai, issue, part, sign, specs, css, pseudo, added, current, work, content, code, projects, closed, behaves, inlinelevel, doesnt, smaller, behavior, loirooriol, commented, container, height, strut, testcase, cssmeetingbot, navigation, pull, requests, actions, security, similar, elements, text, browser, expecting, explain,

Topics {✒️}

[css-inline][css-pseudo] interaction personal information [css-pseudo] fantasai added io/oxydesign/pen/bc9238f85b871ba1059bc43c953c7a46 reduced line-height firefox discussed [css-pseudo] reduced line-height safari css working group root inline box reduced line-height reduced line height [css-pseudo] css inline css properties apply type projects line pseudo-element line pseudo-element line pseudo element inline-level element root inline fragment inline layout properties loirooriol mentioned line-height property smaller line-height line-height affect short code sample code samples shows full irc log comment metadata assignees line boxes inside smaller font-size [css3-text-decor] text decoration properties block-level element text content pseudo element line-pseudo issue raised block container behaves inline-element projects milestone csswg resolution line-height behaves similar inline elements minimum height specs related practical impact font properties content

Payment Methods {📊}

Braintree

Questions {❓}

Already have an account?
It does seem to me that letting the ::first-line’s line-height affect the root inline fragment on the first line is helpful, so maybe we want to resolve on that?
Then, the question is: how do the root inline box and ::first-line interact?

Schema {🗺️}

DiscussionForumPosting:
      context:https://schema.org
      headline:[css-pseudo] ::first-line and line-height
      articleBody:Specs: https://www.w3.org/TR/css-pseudo-4/#first-line-pseudo The part of the specs related to the issue raised: ``` The ::first-line pseudo-element’s generated box behaves similar to that of an inline-level element, but with certain restrictions. The following CSS properties apply to a ::first-line pseudo-element: - all font properties (see [CSS3-FONTS]) - the color and opacity properties (see [CSS3COLOR]) - all background properties (see [CSS3BG]) - any typesetting properties that apply to inline elements (see [CSS3TEXT]) - all text decoration properties (see [CSS3-TEXT-DECOR]) - any inline layout properties that apply to inline elements (see [CSS3LINE]) - any other properties defined to apply to ::first-line by their respective specifications ``` I'm opening this ticket because I've recently used the `::first-line` pseudo element and realized that the `line-height` property for that pseudo element: - is implemented in a different way in each browser - doesn't behave as I was expecting (inline VS block) A short code sample to explain: https://codepen.io/OxyDesign/pen/bc9238f85b871ba1059bc43c953c7a46 (The pseudo element `::first-line` has a smaller `line-height`) - Chrome (63) applies the reduced `line-height` - Firefox (58) doesn't apply the reduced `line-height` - Safari (10) applies the reduced `line-height` but only if the line is not broken with a `<br>`, in that case it doesn't apply the reduced `line-height` - Internet Explorer (I could only have a quick look at 9, 10 and 11) seems to follow the same logic as Chrome So that might not be really clear on that point because each browser seems to have its own interpretation. The second point is that the specs says that it should "behaves similar to that of an inline-level element". I was expecting this to behave as a block-level element. I understand that `::first-letter` should behave as an inline-element as it's part of the text content of a block and is just a part of the line. But `::first-line` is clearly supposed to use the whole width available. Anything that is on this line is included in the `::first-line` definition, therefore should behave like a block in my humble opinion. The code samples shows that the first line has a smaller `font-size`, so indeed I wanted to apply a smaller `line-height` which is not applied by FF and (partially) by Safari because as an inline-level element it shouldn't. But I think this behavior would make only sense for the `::first-letter` as it's part of a line and we don't want the line to be shrink by the `::first-letter`'s `line-height`. But in the `::first-line` case there is no possibility that any other content would be in the same line without being a part of the `::first-line` pseudo element so that shouldn't behave like that I think.
      author:
         url:https://github.com/OxyDesign
         type:Person
         name:OxyDesign
      datePublished:2018-02-06T23:41:00.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:3
      url:https://github.com/2282/csswg-drafts/issues/2282
      context:https://schema.org
      headline:[css-pseudo] ::first-line and line-height
      articleBody:Specs: https://www.w3.org/TR/css-pseudo-4/#first-line-pseudo The part of the specs related to the issue raised: ``` The ::first-line pseudo-element’s generated box behaves similar to that of an inline-level element, but with certain restrictions. The following CSS properties apply to a ::first-line pseudo-element: - all font properties (see [CSS3-FONTS]) - the color and opacity properties (see [CSS3COLOR]) - all background properties (see [CSS3BG]) - any typesetting properties that apply to inline elements (see [CSS3TEXT]) - all text decoration properties (see [CSS3-TEXT-DECOR]) - any inline layout properties that apply to inline elements (see [CSS3LINE]) - any other properties defined to apply to ::first-line by their respective specifications ``` I'm opening this ticket because I've recently used the `::first-line` pseudo element and realized that the `line-height` property for that pseudo element: - is implemented in a different way in each browser - doesn't behave as I was expecting (inline VS block) A short code sample to explain: https://codepen.io/OxyDesign/pen/bc9238f85b871ba1059bc43c953c7a46 (The pseudo element `::first-line` has a smaller `line-height`) - Chrome (63) applies the reduced `line-height` - Firefox (58) doesn't apply the reduced `line-height` - Safari (10) applies the reduced `line-height` but only if the line is not broken with a `<br>`, in that case it doesn't apply the reduced `line-height` - Internet Explorer (I could only have a quick look at 9, 10 and 11) seems to follow the same logic as Chrome So that might not be really clear on that point because each browser seems to have its own interpretation. The second point is that the specs says that it should "behaves similar to that of an inline-level element". I was expecting this to behave as a block-level element. I understand that `::first-letter` should behave as an inline-element as it's part of the text content of a block and is just a part of the line. But `::first-line` is clearly supposed to use the whole width available. Anything that is on this line is included in the `::first-line` definition, therefore should behave like a block in my humble opinion. The code samples shows that the first line has a smaller `font-size`, so indeed I wanted to apply a smaller `line-height` which is not applied by FF and (partially) by Safari because as an inline-level element it shouldn't. But I think this behavior would make only sense for the `::first-letter` as it's part of a line and we don't want the line to be shrink by the `::first-letter`'s `line-height`. But in the `::first-line` case there is no possibility that any other content would be in the same line without being a part of the `::first-line` pseudo element so that shouldn't behave like that I think.
      author:
         url:https://github.com/OxyDesign
         type:Person
         name:OxyDesign
      datePublished:2018-02-06T23:41:00.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:3
      url:https://github.com/2282/csswg-drafts/issues/2282
Person:
      url:https://github.com/OxyDesign
      name:OxyDesign
      url:https://github.com/OxyDesign
      name:OxyDesign
InteractionCounter:
      interactionType:https://schema.org/CommentAction
      userInteractionCount:3
      interactionType:https://schema.org/CommentAction
      userInteractionCount:3

External Links {🔗}(9)

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

8.85s.