FWIW, no bug here in Chrome 69, 70, 72.

reporter@ - Thanks for filing the issue...!!
Could you please provide a sample test file or url to test the issue from TE-end. By navigating to https://goo.gl/ieKous only shows "Some text for the test" and does nothing. If possible please provide a screen cast for better understanding of the issue. This will help us in triaging the issue further.

Thanks...!!

Here is the link to the screen share video that I've made.
https://goo.gl/VeP1Rm

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Reporter, your video in comment 4 shows a completely different case, where Chrome still behaves correctly: your first selector applies to the child <H1> so it stays red.

It should be black, because it's parent has color property set to black which should override the property with universal selector and combinator.

re 7, the C in CSS stands for cascading and that's what's happening here: the child <H1> has an applicable rule which overrides the parent rule so Chrome renders it correctly in red - same as Firefox or even IE and any other CSS-compliant browser.

P.S. here's a simplified html shown in the video:

    <style>
    .a > * { color: red }
    .b { color: blue }
    </style>
    <div class="a b">
      <h1>test</h1>
    </div>

Let me ask you something @woxxom, are you from the Chromium team or maybe from the Google? If not please don't clutter the chat. And if you have some free time learn about specificity and order in CSS it will help you a lot. 

I do agree that ".container" class on the wrapper of the H1 is misleading but this still should work and H1 should get black color instead of the red.

I'm not a Chromium or Google engineer but they can't do anything without a reproducible test case so they won't be even assigned to this issue. I've been trying to create that test case to help triaging the issue, but as I wrote in comment 1 the bug didn't reproduce (the font-size displayed was 1rem). Then you've shown a completely different use case in your video, still without providing a reproducible test case either via a file or URL.

Maybe I've used the wrong term, it should have been "filtering" or "inheritance", not "cascading".
More info in the spec: https://www.w3.org/TR/css-cascade-3/#declared-value
In the video the red color belongs to <H1> which has just one matching rule: .container > * { color: red }
And consequently it wins over the inherited value from another rule for the container: .body-content { color: black }
Sorry if this wasn't helpful, I hope you'll get an answer from a Chromium engineer eventually.

Thanks woxxom for taking a first look at this.
TBH i'd defer to woxxom on matters of CSS inheritance as much as I would most experts. that explanation sounds right on point to me.

thx