Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

Custom HTML Elements

Name: Cudder !MhMRSATORI!fR8duoqGZdD/iE5 2012-07-08 1:29

Does anyone know of any big/important sites that use custom HTML elements i.e. ones that aren't in the spec?

Name: Anonymous 2012-07-08 1:45

4chan

Name: Cudder !MhMRSATORI!fR8duoqGZdD/iE5 2012-07-08 1:52

>>2
No, that was one of the first sites I checked.

Name: Doesn't contribute 2012-07-08 2:02

>>1
Good question.

Name: Anonymous 2012-07-08 21:05

YouTube

Name: Anonymous 2012-07-08 21:39

No.

Name: Anonymous 2012-07-08 22:00

You can make <span> and <div> do anything with CSS and/or Javascript. Also the browser is optimized on the standard tags; let it do what it does best.

Name: Anonymous 2012-07-08 23:27

Use XHTML everyday1




1. And XML Namespaces

Name: Anonymous 2012-07-08 23:32

>>7
i think you meant <div> and <object>.

Name: Anonymous 2012-07-09 0:58

Name: Cudder !MhMRSATORI!fR8duoqGZdD/iE5 2012-07-09 1:17

>>5
No.

>>7
That's what I thought. I'm not asking this because I want to use custom elements, but it might be better to think of the question as "if browsers did not support custom elements at all, are there any large and popular sites that wouldn't work?"

Name: Anonymous 2012-07-09 2:06

>>11
YouTube uses <embed>, which is non-standard.

Name: Cudder !MhMRSATORI!fR8duoqGZdD/iE5 2012-07-09 3:59

Name: Anonymous 2012-07-09 14:05

>>13
HTML5 isn't a standard yet.

Name: Anonymous 2012-07-09 19:23

>>14
It's in proposal by the w3c which means it's most certainly to be the standard. The fact that it isn't official now doesn't mean it'll be any more of a standard when it is officially ratified.

Name: Anonymous 2012-07-09 19:56

>>15
http://www.w3.org/standards/techs/html#drafts
This document may not provide accurate information as the HTML 5 specification is still actively in development.

http://www.w3.org/TR/2012/WD-html5-20120329/
Implementors should be aware that this specification is not stable. Implementors who are not taking part in the discussions are likely to find the specification changing out from under them in incompatible ways.

Name: Anonymous 2012-07-09 22:03

>>17
The document says this disclaimer because that's the nature of working non-ratified standards. In practise, what are the chances that this specific feature will be changed before it is official? I'm will to bet that the chances are very low.

Name: Anonymous 2012-07-09 22:04

>>14
It's already been implemented by all the lastest browsers. That's all that really matters.

http://harmful.cat-v.org/standards/

Name: Anonymous 2012-07-10 0:07

>>18
what a fucking retard.

Name: Cudder !MhMRSATORI!fR8duoqGZdD/iE5 2012-07-10 6:37

>>14-18
It's a non-issue because I doubt the final standard will have over 127 elements.

I was asking about things like using <myelement> <foo> <bar> ... and not elements defined somewhere in some specification, final or not.

Name: Anonymous 2012-07-10 13:08

It's 2012, Cudder. The days of proprietary tags are over. Now it's all about MICROFORMATS.

Name: Cudder !MhMRSATORI!fR8duoqGZdD/iE5 2012-07-11 4:47

>>21
That is mostly irrelevant to what I'm doing, I'm not making a site but just need to get what's already out there to work.

Don't change these.
Name: Email:
Entire Thread Thread List