Featured post

c# - Usage of Server Side Controls in MVC Frame work -

i using asp.net 4.0 , mvc 2.0 web application. project requiremrnt have use server side control in application not possibl in noraml case. ideally want use adrotator control , datalist control. i saw few samples , references in codepleax mvc controllib howwver found less useful. can tell how utilize theese controls in asp.net application along mvc. note: please provide functionalities related adrotator , datalist controls not equivalent functionalities thanks in advace. mvc pages not use normal .net solution makes use of normal .net components impossible. a normal .net page use event driven solution call different methods service side mvc use actions , view completly different way handle things. also, mvc not use viewstate normal .net controlls require. found article discussing mixing of normal .net , mvc.

In HTML5, is it better to use <section> and <h1> instead of <h2>–<h6>? -


in studying on html5's new section tag, i'm wondering handling of h1, h2, h3, h4, h5, , h6 tags...

the html5 specification says "[h1, h2, etc.] elements represent headings their sections" (http://www.w3.org/tr/html5/sections.html#the-h1-h2-h3-h4-h5-and-h6-elements). further in spec's "4.4.11 headings , sections" section, there 3 examples of structuring document apples.

if follow first specification, states heading elements "should represent headings sections," seems third apple example most correct structure (i.e., using h1 tags heading in each section , subsection). using logic seems h2, h3, h4, h5, , h6 tags used rarely, if @ all.

this i'm wondering: should h2, h3, h4, h5, or h6 tags used if, in reality, marking subsections? not make more sense use section tags separate sections, each own header, rather relying on h2, h3, etc. start implicit sections? (the "headers , sections" section talks sections implied using h2, h3, etc.)

perhaps it's relational database knowledge causing bias, creating multiple header tags numbers (h 1, h 2, h 3) seems bad practice, when technically each heading own section or subsection.

what thoughts?

it seems spec states h1 has preference on others:

sections may contain headings of rank, authors encouraged either use h1 elements, or use elements of appropriate rank section's nesting level.

what disturbs me this:

authors encouraged explicitly wrap sections in elements of sectioning content, instead of relying on implicit sections generated having multiple headings in 1 element of sectioning content.

now wonderful got section, article, nav , aside use prevent div-itis. if need explicitly use section element each section end more section elements ever had divs. feel strong case of section-itis coming on.


Comments

Popular posts from this blog

c# - Usage of Server Side Controls in MVC Frame work -

cocoa - Nesting arrays into NSDictionary object (Objective-C) -

ios - Very simple iPhone App crashes on UILabel settext -