Obsolete features, 구시대 유물들

DEV/CSS

Obsolete features, 구시대 유물들

young.gratia 2015. 9. 20. 23:28

http://www.w3.org/TR/html5/obsolete.html

11 Obsolete features

11.2 Non-conforming features

Elements in the following list are entirely obsolete, and must not be used by authors:

아래 나오는 요소들은 완벽하게 시대에 뒤떨어졌으므로 쓰면 안됩니다!

applet

Use embed or object instead.

acronym

Use abbr instead.

bgsound

Use audio instead.

dir

Use ul instead.

frame

frameset

noframes

Either use iframe and CSS instead, or use server-side includes to generate complete pages with the various invariant parts merged in.

hgroup

To mark up subheadings, consider putting the subheading into a p element after the h1-h6 element containing the main heading, or putting the subheading directly within the h1-h6 element containing the main heading, but separated from the main heading by punctuation and/or within, for example, a span class="subheading" element with differentiated styling.

Headings and subheadings, alternative titles, or taglines can be grouped using the header or div elements.

isindex

Use an explicit form and text field combination instead.

listing

Use pre and code instead.

nextid

Use GUIDs instead.

noembed

Use object instead of embed when fallback is necessary.

plaintext

Use the "text/plain" MIME type instead.

strike

Use del instead if the element is marking an edit, otherwise use s instead.

xmp

Use pre and code instead, and escape "<" and "&" characters as "<" and "&" respectively.

basefont

big

blink

center

font

marquee

multicol

nobr

spacer

tt

Use appropriate elements or CSS instead.

Where the tt element would have been used for marking up keyboard input, consider the kbd element; for variables, consider the var element; for computer code, consider the code element; and for computer output, consider the samp element.

Similarly, if the big element is being used to denote a heading, consider using the h1 element; if it is being used for marking up important passages, consider the strong element; and if it is being used for highlighting text for reference purposes, consider the mark element.

See also the text-level semantics usage summary for more suggestions with examples.

The following attributes are obsolete (though the elements are still part of the language), and must not be used by authors:

아래 속성들 역시 구시대의 유물이므로 (비록 이 속성들을 가지고 있는 요소들은 아직도 쓰일지라도) 쓰면 안됩니다!

charset on a elements
charset on link elements: Use an HTTP Content-Type header on the linked resource instead.
coords on a elements
shape on a elements: Use area instead of a for image maps.
methods on a elements
methods on link elements: Use the HTTP OPTIONS feature instead.
name on a elements (except as noted in the previous section)
name on embed elements
name on img elements
name on option elements: Use the id attribute instead.
urn on a elements
urn on link elements: Specify the preferred persistent identifier using the href attribute instead.
accept on form elements: Use the accept attribute directly on the input elements instead.
nohref on area elements: Omitting the href attribute is sufficient; the nohref attribute is unnecessary. Omit it altogether.
profile on head elements: When used for declaring which meta terms are used in the document, unnecessary; omit it altogether, and register the names.; When used for triggering specific user agent behaviors: use a link element instead.
version on html elements: Unnecessary. Omit it altogether.
ismap on input elements: Unnecessary. Omit it altogether. All input elements with a type attribute in the Image Button state are processed as server-side image maps.
usemap on input elements: Use img instead of input for image maps.
lowsrc on img elements: Use a progressive JPEG image (given in the src attribute), instead of using two separate images.
target on link elements: Unnecessary. Omit it altogether.
scheme on meta elements: Use only one scheme per field, or make the scheme declaration part of the value.
archive on object elements
classid on object elements
code on object elements
codebase on object elements
codetype on object elements: Use the data and type attributes to invoke plugins. To set parameters with these names in particular, the param element can be used.
declare on object elements: Repeat the object element completely each time the resource is to be reused.
standby on object elements: Optimize the linked resource so that it loads quickly or, at least, incrementally.
type on param elements
valuetype on param elements: Use the name and value attributes without declaring value types.
language on script elements (except as noted in the previous section): Use the type attribute instead.
event on script elements
for on script elements: Use DOM Events mechanisms to register event listeners. [DOM]
datapagesize on table elements: Unnecessary. Omit it altogether.
summary on table elements: Use one of the techniques for describing tables given in the table section instead.
axis on td and th elements: Use the scope attribute on the relevant th.
scope on td elements: Use th elements for heading cells.
datasrc on a, applet, button, div, frame, iframe, img, input, label, legend, marquee, object, option, select, span, table, and textarea elements
datafld on a, applet, button, div, fieldset, frame, iframe, img, input, label, legend, marquee, object, param, select, span, and textarea elements
dataformatas on button, div, input, label, legend, marquee, object, option, select, span, and table elements: Use script and a mechanism such as XMLHttpRequest to populate the page dynamically. [XHR]
alink on body elements
bgcolor on body elements
link on body elements
marginbottom on body elements
marginheight on body elements
marginleft on body elements
marginright on body elements
margintop on body elements
marginwidth on body elements
text on body elements
vlink on body elements
clear on br elements
align on caption elements
align on col elements
char on col elements
charoff on col elements
valign on col elements
width on col elements
align on div elements
compact on dl elements
align on embed elements
hspace on embed elements
vspace on embed elements
align on hr elements
color on hr elements
noshade on hr elements
size on hr elements
width on hr elements
align on h1—h6 elements
align on iframe elements
allowtransparency on iframe elements
frameborder on iframe elements
hspace on iframe elements
marginheight on iframe elements
marginwidth on iframe elements
scrolling on iframe elements
vspace on iframe elements
align on input elements
hspace on input elements
vspace on input elements
align on img elements
border on img elements (except as noted in the previous section)
hspace on img elements
vspace on img elements
align on legend elements
type on li elements
align on object elements
border on object elements
hspace on object elements
vspace on object elements
compact on ol elements
align on p elements
width on pre elements
align on table elements
bgcolor on table elements
bordercolor on table elements
cellpadding on table elements
cellspacing on table elements
frame on table elements
rules on table elements
width on table elements
align on tbody, thead, and tfoot elements
char on tbody, thead, and tfoot elements
charoff on tbody, thead, and tfoot elements
valign on tbody, thead, and tfoot elements
align on td and th elements
bgcolor on td and th elements
char on td and th elements
charoff on td and th elements
height on td and th elements
nowrap on td and th elements
valign on td and th elements
width on td and th elements
align on tr elements
bgcolor on tr elements
char on tr elements
charoff on tr elements
valign on tr elements
compact on ul elements
type on ul elements
background on body, table, thead, tbody, tfoot, tr, td, and th elements: Use CSS instead.

The border attribute on the table element can be used to provide basic fallback styling for the purpose of making tables legible in browsing environments where CSS support is limited or absent, such as text-based browsers, WYSIWYG editors, and in situations where CSS support is disabled or the style sheet is lost. Only the empty string and the value "1" may be used as border values for this purpose. Other values are considered obsolete. To regulate the thickness of such borders, authors should instead use CSS.

음 글자색을 입히다가 너무 많아서 포기했다.

아무튼 쓰지 말라고 하시니 절대 쓰지말자!

저작자표시 비영리 변경금지