Databases
StackOverflow2013
Postsdbo
POHow do you use HTML5 tags while supporting Progressive Enhancement for no-script clients that don't natively recognize unknown elements?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow do you use HTML5 tags while supporting Progressive Enhancement for no-script clients that don't natively recognize unknown elements?
    primarykey
    data
    text
    <p>As I understand Progressive Enhancement, one of the basic tenets is the web site should be functional for <em>everyone</em>, regardless of browser version or settings. </p> <p>The suggested breakdown I've seen is:</p> <ul> <li>HTML content layer using semantic markup</li> <li>CSS Presentation layer</li> <li>Enhancement layer (typically through JavaScript or a JS library like JQuery)</li> </ul> <p>I'm a bit confused over the proper way to handle the HTML content layer, however. In particular, the semantic markup.</p> <p>I keep seeing that HTML5 tags such as nav, article, footer etc. are the ideal method of maintaining this semantic markup for PE. However, many older browsers do not support HTML5 tags. The easy way to get around this is to use CSS to set default stylings to { display: block; } for the HTML5 tags, but this only works with some browsers. The dreaded IE6, for example, does not recognize HTML5 elements.</p> <p>The typical workaround for this is to use javascript to dynamically create the missing elements directly into the DOM (such as through an HTML5 shiv).</p> <p>However... if the client is running an environment that doesn't recognize HTML5 elements, <strong>and</strong> they do not, for whatever reason, accept javascript, how do you incorporate HTML5 semantic tags in support of Progressive Enhancement, without failing to render properly for scriptless browsers that don't recognize the tags? Is this possible, or do you have to leave those browsers out of your design consideration (which seems counter to the PE ideals)? </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRobert Harvey
    1. USBeofett
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow do you use HTML5 tags while supporting Progressive Enhancement for no-script clients that don't natively recognize unknown elements?
      1. USJosé M. Pérez
      1. VTFavorite
    2. VO
      singulars
      1. POHow do you use HTML5 tags while supporting Progressive Enhancement for no-script clients that don't natively recognize unknown elements?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow do you use HTML5 tags while supporting Progressive Enhancement for no-script clients that don't natively recognize unknown elements?
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODo I have to read all this, or just the title of your question? :)
      singulars
      1. POHow do you use HTML5 tags while supporting Progressive Enhancement for no-script clients that don't natively recognize unknown elements?
      1. USRobert Harvey
    2. CO@RobertHarvey With my edit, just the title :)
      singulars
      1. POHow do you use HTML5 tags while supporting Progressive Enhancement for no-script clients that don't natively recognize unknown elements?
      1. USBeofett
    3. COIE6 is pretty much dead: http://www.ie6countdown.com/. So many sites these days require JavaScript and provide no fallback if it is disabled, I can't imagine anyone disabling JS on purpose anymore (other than to turn off poorly written JS that makes the site unusable).
      singulars
      1. POHow do you use HTML5 tags while supporting Progressive Enhancement for no-script clients that don't natively recognize unknown elements?
      1. UScimmanon
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload