There may be a compelling reason to make an additive change to the standard, one that doesn't break any sites. We should listen over the next few months and be more open to such a change than to a breaking change. On Thu, Sep 11, 2014 at 6:48 PM, Michael Riethmuller < michael.riethmuller@gmail.com> wrote: > I don't have an insiders perspective on the lifecycle of standards. But > I'd agree with the statement "once people start using it, it can't > change". -To be on the safe side I might replace "can't" with > very unlikely. > > I think history demonstrates that once it is implemented, if it does > change, it will be a long time before the browsers drop support for the > depreciated methods. > > To give an example <center> and <font> were depreciated in HTML4 but > continue to work in the latest versions of most browsers. > > If it does change I'd say companies will have time to adapt. > > Mike > > On Fri, Sep 12, 2014 at 8:24 AM, Marcos Caceres <marcos@marcosc.com> > wrote: > >> >> >> >> On September 11, 2014 at 6:16:12 PM, Jason Grigsby (jason@cloudfour.com) >> wrote: >> > > >> > I'd love to hear from someone with more perspective on the lifecycle >> > of standards about how confident we should feel that picture >> > will stay as currently spec'd. Is it common that features like >> > this get tweaked a little in the future as people start using them >> > and an oversight is found? Should we still be hedging our bets >> > a little? Or does it seem extremely unlikely to change at this >> > point? >> >> Once it gets into the wild and people start using it, it can't change. >> Thems is the golden rule of the Web. >> >> Spec is stable and the browsers are coming this month - go forth and >> <picture> all the things! Make the web beautiful again :) >> >> >
Received on Friday, 12 September 2014 13:25:44 UTC