Content deleted Content added
Line 42:
::Then it must be me, but I still don't get it how something can be a standard if it's in constant flux. The moment you stop reading, your information may already be outdated. Still, thanks for the reply, I'll try to think it over a few times, maybe I'll understand then. --[[User:Cyberman TM|Cyberman TM]] ([[User talk:Cyberman TM|talk]]) 07:42, 11 April 2013 (UTC)
:::The point of it is that it evolves, but everyone is using the same hymnsheet. In general, things that have been standardised already in html5 are not altered significantly in an update, so you're unlikely to be incompatible with html5 if you've read an older version of it. The updates generally deal with new elements, or new ways of dealing with background methods regarding new elements. Older versions of the html5 standard are still classed as html5, so they are still supported, but new 'bits' are being added to flesh it out. None of the updates say "forget everything so far. This is html5 now", they say things like "remember this feature, well now we're added a new one alongside it." <span style="background-color:#6CF;border:1px solid #09F;padding:0px 5px;border-radius:99px">[[User:Sonicdrewdriver|drewmunn]] <span style="border-left:1px solid #09F;padding-left:5px">[[User talk:Sonicdrewdriver|talk]]</span></span> 08:35, 11 April 2013 (UTC)
::::The sentence now reads "''The WHATWG organization will continue its work with HTML5 as a "Living Standard". The concept of a living standard is that it is never complete and is always being updated and improved. '''New features can be added but functionality will not be removed.'''''" Does this make it clearer? I would agree that before its hard to see how something can be a standard and a living standard at the same time.
| |||