<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>HTML5 Specification on HTML5 in 24 Hours</title>
    <link>https://www.html5in24hours.com/tags/html5-specification/</link>
    <description>HTML5 Specification on HTML5 in 24 Hours</description>
    <generator>Hugo</generator>
    <language>en-us</language><copyright>Jennifer Kyrnin</copyright><lastBuildDate>Sat, 05 Nov 2011 18:10:16 +0000</lastBuildDate>
    <atom:link href="https://www.html5in24hours.com/tags/html5-specification/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Blink and you missed it. TIME element back in the HTML5 spec</title>
      <link>https://www.html5in24hours.com/errata/blink-and-you-missed-it-time-element-back-in-the-html5-spec/</link>
      <pubDate>Sat, 05 Nov 2011 18:10:16 +0000</pubDate>
      <guid>https://www.html5in24hours.com/errata/blink-and-you-missed-it-time-element-back-in-the-html5-spec/</guid><description>&lt;h2 id=&#34;from-sams-teach-yourself-html5-mobile-application-development-in-24-hours&#34;&gt;from: Sams Teach Yourself HTML5 Mobile Application Development in 24 Hours&lt;/h2&gt;&#xA;&lt;p&gt;After a large uproar by designers and developers last week when they removed the HTML5 &lt;code&gt;TIME&lt;/code&gt; element, the W3C recanted and put it back in the spec. So you don&amp;rsquo;t have to replace &lt;code&gt;TIME&lt;/code&gt; with &lt;code&gt;DATA&lt;/code&gt;, but you can if you want to.&lt;/p&gt;&#xA;&lt;p&gt;This corrects last week’s errata post. The book still contains the &lt;code&gt;TIME&lt;/code&gt; element, but does not contain the &lt;code&gt;DATA&lt;/code&gt; element.&lt;/p&gt;&#xA;&lt;p&gt;What&amp;rsquo;s really great is that this shows that the W3C is listening to us. So if there is some other problem with the HTML5 spec, don&amp;rsquo;t be shy—let them know. If enough agree, your change may happen!&lt;/p&gt;&#xA;</description>
    </item>
    <item>
      <title>Borders on tables now ok in HTML5</title>
      <link>https://www.html5in24hours.com/posts/borders-on-tables-now-ok-in-html5/</link>
      <pubDate>Fri, 22 Apr 2011 16:05:05 +0000</pubDate>
      <guid>https://www.html5in24hours.com/posts/borders-on-tables-now-ok-in-html5/</guid><description>&lt;p&gt;If you use tables (not for layout, of course) it can be very tedious to get the borders to surround every cell using CSS. You need to set the border on the table and on every th and td, and then collapse the borders with border-collapse. I don’t know about you, but I would often just add the &lt;code&gt;border&lt;/code&gt; attribute to the table, just to get it done quickly.&lt;/p&gt;&#xA;&lt;p&gt;Well, this week the HTML5 working group &lt;a href=&#34;http://www.w3.org/html/wg/wiki/ISSUE-155-CP1&#34;&gt;decided&lt;/a&gt; to make that okay again. They agreed that many tables need to have borders to define the cells. The &lt;a href=&#34;http://lists.w3.org/Archives/Public/public-html/2011Apr/0377.html&#34;&gt;proposal&lt;/a&gt; pointed out that putting CSS on a table to define the borders would not be carried over when the table was moved between implementations. In other words, if you wrote a table in an HTML document, and then ported that document into XML, the borders in CSS would stay with the CSS, not with the table.&lt;/p&gt;&#xA;&lt;h2 id=&#34;now-it-is-legal-to-write-table-borderto-add-borders-around-your-table-and-table-cells-i-for-one-am-pleased&#34;&gt;Now it is legal to write &lt;code&gt;&amp;lt;table border&amp;gt;&lt;/code&gt;  to add borders around your table and table cells. I, for one, am pleased!&lt;/h2&gt;&#xA;&lt;h3 id=&#34;comments&#34;&gt;Comments:&lt;/h3&gt;&#xA;&lt;h4&gt;&lt;/h4&gt;&#xA;&lt;p&gt;&lt;a href=&#34;%22skmpu@bhmk.com%22&#34;&gt;Steven K. Mariner&lt;/a&gt; - Mar 5, 2015&lt;/p&gt;&#xA;&lt;p&gt;This is good news and a welcome relief. I was starting to wonder if the fine folks who worked on the HTML5 standard even used HTML anymore. The insane amount of overhead required by the use of CSS to do everything suggested they have forgotten that sometimes *people* make web sites, and mobile devices have to load them *slowly*. Mandatory content increase is a bad idea, and HTML5 is littered with it.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;</description>
    </item>
    <item>
      <title>HTML5 last call now has a date</title>
      <link>https://www.html5in24hours.com/posts/html5-last-call-now-has-a-date/</link>
      <pubDate>Tue, 19 Apr 2011 16:29:57 +0000</pubDate>
      <guid>https://www.html5in24hours.com/posts/html5-last-call-now-has-a-date/</guid><description>&lt;p&gt;According to &lt;a href=&#34;http://www.itpro.co.uk/632938/html5-standards-deadline-set-for-24-may&#34;&gt;IT Pro&lt;/a&gt;, the W3C has set a deadline of &lt;strong&gt;May 24, 2011&lt;/strong&gt; for the last issues to be delivered about the HTML5 specification.&lt;/p&gt;&#xA;&lt;p&gt;This is exciting news for the standard, as it means that browser makers will start building to it in earnest, web designers can be more confident that the sites they build won&amp;rsquo;t need hacks, and HTML5 will grow in popularity and importance.&lt;/p&gt;&#xA;</description>
    </item>
  </channel>
</rss>
