Version targeting
 | This article is actively undergoing a major edit for a little while. To help avoid edit conflicts, please do not edit this page while this message is displayed. This page was last edited at 15:13, 1 September 2008 (UTC) (16 years ago) – this estimate is cached, . Please remove this template if this page hasn't been edited for a significant time. If you are the editor who added this template, please be sure to remove it or replace it with {{Under construction}} between editing sessions. |
In computing, version targeting is a technique that allows a group of (presumably knowledgeable) users utilise some advanced software features that were introduced in a particular software version while allowing users accustomed to the prior versions still utilise the same software as if the new features were never added to the software. It is a way to ensure backwards compatibility when new software features would otherwise break it.
In Mozilla Firefox
Version targeting has been used in Mozilla Firefox[1] when it introduced JavaScript 1.6 in Firefox 1.5[2] and JavaScript 1.7 in Firefox 2.0[3]: developers willing to use the new scripting engine had to explicitly opt-in.[1]
Proposed utilisation in Internet Explorer
Version targeting was also a proposed by Microsoft for utilisation in its Internet Explorer 8 product-in-development but the idea was later thrown out of consideration.[4]
The proposal came after the release of Internet Explorer 7 which improved its CSS 2.1 support at the cost of causing some websites that were developed for Internet Explorer 6 to be rendered incorectly under the new browser version.[5]
See also
References
- ^ a b http://www.alistapart.com/articles/minorthreat
- ^ http://developer.mozilla.org/en/New_in_JavaScript_1.6
- ^ http://developer.mozilla.org/en/New_in_JavaScript_1.7#Using_JavaScript_1.7
- ^ http://blogs.msdn.com/ie/archive/2008/03/03/microsoft-s-interoperability-principles-and-ie8.aspx
- ^ http://www.alistapart.com/articles/beyonddoctype