history - Why are h1-h6 different tag names in HTML? -


why h1 through h6 different tags in html, rather having syntax <heading level="1">? i'd interested know history behind decision (and same different lists, ol , ul rather common list).

so far, research hasn't turned up. w3c spec groups them "headings", describing them jointly. asked similar question on stack overflow once before, discussion value of semantics , not reasoning particular language design choice.

edit: i'm not asking seo implications of 1 or other, i'm looking answers around why creators of html chose syntax did.

edit 2: question can elicit lot of opinion there exists factual answer, , found jukka in comments below: http://infomesh.net/html/history/early/. assumed opinion part of discussion had when html first created, , looking rather trying rehash debate.

why h1 through h6 different tags in html, rather having syntax <heading level="1">?

because that's how defined in 1993:

headings     6 levels  of heading supported. (note hypertext node    within hypertext work tends need less levels of  heading    work structure given nesting of headings.)     heading element implies font changes, paragraph breaks    before , after, , white space (for example) necessary render    heading. further character emphasis or paragraph marks not    required in html.     h1 highest level of heading, , recommended    start of hypertext node.   suggested the text of    first heading suitable reader browsing    in related information, in contrast title tag should    identify node in wider context.     heading elements                  <h1>, <h2>, <h3>, <h4>, <h5>, <h6>

you must realize there minimal attribute usage in original html spec. each element served specific purpose toward marking documents emphasis on being easy write , easy read. can assume tag along lines of <heading> have been flat-out rejected because long type, , in way of content of page.

the usage predates concept of external stylesheets, selectors not have played role in decision naming convention.

once elements defined, there no reason rename them cause backwards compatibility issues.


Comments

Post a Comment

Popular posts from this blog

c# - Send Image in Json : 400 Bad request -

from android trying send image class of data, iis webservice. (c#) the problem 400 bad request . the image being encoded base64 . , placed json rest of class elements. my guess base64 not valid inside json. server not understand it. if set string "" , post accepted fine. so question is, how make base64 valid within json array? ( tried url.encode no success). or how should send image android webservice? gson gson = new gson(); string json = gson.tojson(record); // record has param { string base64photo } how big image? i'm pretty sure surpassing iis json size limit (default 4 mb). check http://geekswithblogs.net/frankw/archive/2008/08/05/how-to-configure-maxjsonlength-in-asp.net-ajax-applications.aspx or http://www.webtrenches.com/post.cfm/iis7-file-upload-size-limits good luck!
Read more

javascript - addthis share facebook and google+ url -

i attempting use addthis create simple url shares whichever current page user on when click share button. of right now, have twitter working. when user clicks, able see url populated in tweet box. when user clicks facebook or google+, url doesn't seem show in share box. <ul class="addthis_toolbox addthis_default_style "> <li><a class="addthis_button_facebook"><img src="/img/facebook-social.png" width="20" height="20" border="0" alt="share" /></a></li> <li><a class="addthis_button_twitter"><img src="/img/twitter-social.png" width="20" height="20" border="0" alt="share" /></a></li> <li><a class="addthis_button_google_plusone_share"><img src="/img/google-social.png" width="20" height="20" border="0" alt="s...
Read more

ios - Show keyboard with UITextField in the input accessory view -

i have buttona , when buttona clicked, want keyboard show uitextfield in inputaccessoryview. there way have keyboard show manually , set inputaccessoryview without having uitextfield initially? thanks. you cannot summon keyboard without object can become first responder. there 2 ways work around: subclass uiview , implement uikeyinput protocol in it. example: in .h file: @interface inputobject : uiview<uikeyinput> @property (nonatomic, copy) nsstring *text; @property (nonatomic, strong) uiview *inputaccessoryview; // must override inputaccessoryview , since it's readonly default @end in .m file, implement protocol: - (bool)canbecomefirstresponder { return yes; } - (bool)hastext { return [self.text length]; } - (void)inserttext:(nsstring *)text { nsstring *selftext = self.text ? self.text : @""; self.text = [selftext stringbyappendingstring:text]; [[nsnotificationcenter defaultcenter] postnotificationname:kinputobjec...
Read more