In computing, version targeting is a technique that allows a group of (presumably knowledgeable) users (including software developers) to use some advanced software features that were introduced in a particular software version while allowing users accustomed to the prior versions to still use the same software as if the new features were never added to the software. It is a way to ensure backward 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]

Use in Internet Explorer

Version targeting was proposed by Microsoft for use in its Internet Explorer 8 product-in-development, but the idea was later discarded.[4][5]

The proposal came after the release of Internet Explorer 7 which improved its CSS 2.1 support[6] at the cost of causing some websites that were developed for Internet Explorer 6 to be rendered incorrectly when viewed with the new browser version.[7][8]

Microsoft contacted the Web Standards Project and experts on Web standards and asked for assistance in devising a new DOCTYPE-like technique that could work across browsers and let Web developers specify exact browser versions under which their Web sites are known to work correctly, and browsers implementing this form of version targeting would use the correct rendering engine versions to display the site correctly.[7] Members of the WaSP Microsoft Task Force were involved in the proposal, albeit not every member backed it.[9]

Some commentators suggested that it would be possible to use Internet Explorer 8's support for new DOCTYPEs in order to avoid using its version targeting meta tag.[10]

Criticism

The concept of version targeting, especially as proposed by Microsoft, has been criticised for being a new form of browser sniffing and for violating the principle of forward-compatible development where progressive enhancement is preferred.[11]

Version targeting has been criticised for not giving incentives to developers to plan ahead for forward compatibility.[11]

Positive reception

Version targeting has been welcomed by some people as a means to enable browsers to adopt Web standards without breaking compatibility with Web sites depended on old rendering engines for their functionality.[12]

References

  1. 1 2 "Version Targeting: Threat or Menace?". 19 February 2008.
  2. ↑ "New in JavaScript 1.6 - Mozilla Developer Center". developer.mozilla.org. Archived from the original on 2008-08-23.
  3. ↑ "New in JavaScript 1.7 - Mozilla Developer Center". developer.mozilla.org. Archived from the original on 2008-08-22.
  4. ↑ "IEBlog". 17 July 2020.
  5. ↑ "Microsoft Backflips on Browser Version Targeting - SitePoint". 4 March 2008.
  6. ↑ Mielke, Markus; Massy, Dave (2006-01-31). "Cascading Style Sheet Compatibility in Internet Explorer 7". Microsoft Developer Network. Microsoft. Retrieved 2016-12-26.
  7. 1 2 "Beyond DOCTYPE: Web Standards, Forward Compatibility, and IE8". 22 January 2008.
  8. ↑ "IE7: Were they ready?". 2006-10-26. Archived from the original on 2018-01-30. Retrieved 2024-01-03.
  9. ↑ "Microsoft's Version Targeting Proposal - the Web Standards Project". Archived from the original on October 2, 2008. Retrieved September 2, 2008.
  10. ↑ "John Resig - HTML5 DOCTYPE".
  11. 1 2 "From Switches to Targets: A Standardista's Journey". 23 January 2008.
  12. ↑ "In defense of version targeting". 22 January 2008.

Bibliography

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.