Propose an Element

[miniajuer]

I thought it might be fun to see what ideas people had for HTML that aren't exactly being considered by the W3C, or just currently aren't read by web browsers in any way.

For example, I think a <noparse> element could be useful for displaying code, where any code contained inside this element is NOT parsed by the browser (<noparse>HTML Code</noparse>). This way people can post tutorials and such without having to resort to the special character codes of [FONT=Verdana,Arial,Helvetica]&lt; for the < sign, [FONT=Verdana,Arial,Helvetica]&gt; for the > sign, ​

[FONT=Verdana,Arial,Helvetica]etc.[/FONT]

So if anyone had any ideas for new elements, post the tag, whether it's self closing or not, and the description of what it's purpose is.

If people also had ideas for new attributes or values, those sound interesting to hear too.[/FONT]​

[/FONT]

 

[Cogman]

The <w3getyourstufftogether> tag. A magical tag that causes a certain comity to commit on a standard and release it so we don't have to deal with all these browser incompatabilities/speculations.

 

[PhatoseAlpha]

Ah, but that tag will get you nothing more then a standard, and as history has shown, standards don't actually prevent incompatibilities.

You need the <directdivineintervention> tag.


Can we include css in these? I want "margin-top: autocenter" for vertical spacing, and things "width: 100&#37;-30px"

 

[Cogman]

Ah, but that tag will get you nothing more then a standard, and as history has shown, standards don't actually prevent incompatibilities.

You need the <directdivineintervention> tag.


Can we include css in these? I want "margin-top: autocenter" for vertical spacing, and things "width: 100%-30px"

My feeling is that the reason for incompatibilities now is the fact that there is no standard. Browser developers are grappling and struggling to try and implement features that W3 starts to imply might be included. Where they to say "these are the standards, implement them" I think we would see better adoption (though, not perfect.)

Oh, and I agree. something that allows us to do what the <center> tag did would be nice, it is silly that functionality doesn't really exist in CSS (not without a lot of hackery).

 

[Aluvus]

My feeling is that the reason for incompatibilities now is the fact that there is no standard. Browser developers are grappling and struggling to try and implement features that W3 starts to imply might be included. Where they to say "these are the standards, implement them" I think we would see better adoption (though, not perfect.)

Oh, and I agree. something that allows us to do what the <center> tag did would be nice, it is silly that functionality doesn't really exist in CSS (not without a lot of hackery).

CSS1 and CSS2 have been standards for a good while (CSS2 became a W3C Recommendation in 1998), and yet browser implementations of them remain inconsistent. In part, this is just because the standard itself is painfully complicated. Cross-platform support of complex standards among adversaries is a hard problem. None of this is to say that the current, horribly drawn-out approach that the W3C uses is great; but the problem is multifaceted.

And yes, being able to easily do a "center with offset" in CSS would make life easier. Just as it would be nice to easily do a lot of common designs that currently require either a touch of wizardry or HTML tables. CSS3 somewhat addresses some of my personal gripes, but not all of them.