[mushyhammer]

Contrary to popular belief, HTML and CSS are unrelated.

If any CSS property was also an HTML attribute, any addition to either spec would have to make sure it wouldn’t conflict. One example is the `content` HTML attribute and CSS property. They serve different purposes and have a completely different syntax.

    <meta name="description" content="Cool stuff”>

and

    .css::before {
        content: url(image.bmp)
    }

[tannhaeuser]

Thanks for lecturing me, I'm aware of all that and know the genesis myth of CSS ;)

Sorry but I think you guys/gals don't get it - the question is why do we need two item-value syntaxes. Like, HTML has 'bgcolor=black' as markup attribute, and owing to SGML, the effective value for that attribute can be defaulted, inherited, and assigned in a context-dependent way. Those mechanisms aren't directly part of HTML because they don't need to be when it's understood that HTML as an SGML application can of course make use of all the authoring mechanism SGML has. But then comes CSS and defines an entirely new syntax that's almost the same (eg. "background: #000"). How is that helpful?

To say it in another way: let's assume we want web pages in 3D space, and yes I know z-index and CSS parallax effect are a thing so bear with me. Following the CSS logic, we should tunnel a background depth/z coordinate via CSS-in-HTML, like

    <p style="background-image: url(bla); 3d-props: 'z is -100angstrom, depth-of-field is 123deg'">

where I deliberately have chosen ad-hoc characters for the item/value separator and multiple-properties separator to make the point.

You know, having a common meta syntax for elements/attributes is the entire point of SGML as a text format after all ;)

[mushyhammer]

You don’t like my “lecturing,” but you continue making preposterous statements and asking questions that can’t be answered without “lecturing.” It’s like you’re saying “why is the sky is blue when we have water?” and then correcting yourself with “but I was talking about the stars, dude. ;)”

To answer pragmatically:

- don’t use the style attribute

- you could use XLST, which is style (and more) that uses the same ML

- are you suggesting that CSS and HTML should have the same style? <a style=“color=\”red\””>? I don’t know how that’s better.

Maybe you’re still missing some lecturing: HTML is content and CSS is style. What you’re saying about 3D context would be specified in CSS, in a separate file, so your CSS-in-HTML readability argument (I guess that’s your argument? Who knows) falls pretty flat.

It’s almost the same as complaining that JS doesn’t have the same format as HTML while it totally could, but instead we have JS-in-HTML. Oh how unfair life is.

As far as I can see, you’re just trolling, so thanks for the laughs.

Signed,

    <a onclick="this.style.background='url(<svg title=\"&#x1F595;\"><rect fill=\"blue\"/></svg>)'">

[ttybird2]

You are missing the point. Their issue is that we have two different syntaxes for specifying key-value attributes.

"are you suggesting that CSS and HTML should have the same style? <a style=“color=\”red\””>?"

Probably more like <a css-color="red"> - or alternatively: <a id=xxx> and in an css file: .xxx { href: "http..." }

I also think that you need to chill.

[mushyhammer]

What you’re saying was not clear from the start, you keep moving the goalpost.

Ironically XML allowed namespaces so css:color="red" could have totally been a thing. However CSS came out to separate content from style, so doing that wouldn’t have made much sense. I wouldn’t be surprised if the style attribute was added later.

Edit: wow I was right:

> HTML 3.0 supports style sheets via the use of the LINK element [1]

> HTML 4.0 adds new hooks for style sheets, which suggest how a document is presented. The new ID, CLASS, and STYLE attributes [2]

[1]: https://www.w3.org/MarkUp/html3/intro.html

[2]: https://www2.cs.sfu.ca/~ggbaker/reference/wdghtml401/new.htm...

[ttybird2]

"you keep moving the goalpost."

This is my first post in this thread... And no, it is not moving any goalpost.

"However CSS came out to separate content from style, so doing that wouldn’t have made much sense"

The first is true, but it does not imply the second.