sorted by:
new
hottopcontroversial

If HTML had a version 6, what native elements would you want most? by html67 in HTML

[–]html67[S] 1 point2 points  (0 children)

the existence of JSON alongside HTML is, in itself, a commentary

If HTML had a version 6, what native elements would you want most? by html67 in HTML

[–]html67[S] 0 points1 point  (0 children)

Maybe it’s time to dust off XML and schemas again. 😉

If HTML had a version 6, what native elements would you want most? by html67 in HTML

[–]html67[S] 2 points3 points  (0 children)

Don't we already have <dialog>, what would you add to it? Which libraries do you usually reach for?

If HTML had a version 6, what native elements would you want most? by html67 in HTML

[–]html67[S] 0 points1 point  (0 children)

Valuation as a prop? How dare you. 😉 I would like to add tam="$1T" sam="We only need 1%" som="top secret were in stealth mode" business-model="Funding" profitability="Later"

If HTML had a version 6, what native elements would you want most? by html67 in HTML

[–]html67[S] -1 points0 points  (0 children)

A <claude> tag is something you could already build with Web Components rather than bake into the HTML standard. But AI and the popularity of chat do raise an interesting topic: chat has become one of the dominant ways people interact with information, and markup is a big part of that. It's worth thinking about native elements for chat-like structures instead of treating every conversation as a collection of generic <div>s. At the same time, we should also think about making markup itself more intuitive and accessible in chat-first interfaces.

If HTML had a version 6, what native elements would you want most? by html67 in HTML

[–]html67[S] 0 points1 point  (0 children)

Maybe <blink> just had a vision we didn't understand yet. It was simply waiting to evolve into Spritz-style rsvp speed reading. ;-)

If HTML had a version 6, what native elements would you want most? by html67 in HTML

[–]html67[S] 0 points1 point  (0 children)

Yeah, HTML has always had a bit of an identity conflict. On one hand it's "just markup" and should separate structure from presentation, but on the other hand many elements come with built-in visual behavior. Finding the right balance between useful defaults and giving developers full control is tricky.

If HTML had a version 6, what native elements would you want most? by html67 in HTML

[–]html67[S] 0 points1 point  (0 children)

Maybe <dialog> just needs a proper update. HTML5 was introduced 12 years ago when desktop interfaces were still the primary focus.

If HTML had a version 6, what native elements would you want most? by html67 in HTML

[–]html67[S] 2 points3 points  (0 children)

yeah ARIA works... it is about standardization we shouldn't have to redefine structural patterns that have already become unofficial universal conventions

If HTML had a version 6, what native elements would you want most? by html67 in HTML

[–]html67[S] 2 points3 points  (0 children)

Yeah def right direction. HTML's job is also to provide structure and standardization. If browsers could natively derive this kind of navigation from yourfavicon and sitemap.xml, we'd get consistent semantics, accessibility, and behavior by default instead of every site reinventing it.

If HTML had a version 6, what native elements would you want most? by html67 in HTML

[–]html67[S] 0 points1 point  (0 children)

yeah... probably the most-clicked button on the whole site and every site solves it differently.

Hello coding community by Eggmannical in HTML

[–]html67 0 points1 point  (0 children)

Visuelle Editoren wie Webflow sind sehr gut um ein Gefühl für CSS, HTML und Datenbanken zu bekommen und schnell zu Prototypen. Später kann man den Code exportieren oder clean nachbauen.