Over 90% of the personal computer operating systems in the world are Windows. As a result, application developers often use Microsoft tools to help write programs that work with Windows, and with related technologies or products that are integrated or often used with Windows. Microsoft has a history of using its tools to lock out other products. For example, Microsoft web development tools have often resulted in code that only works with IE. The application developers may or may not even be aware of this. They use a convenient tool provided by the operating system vendor, and end up helping extend the operating system monopoly to other products.
Examples of tools to which this principle would apply include Microsoft Expression Web and Microsoft Office Sharepoint. One might also include Silverlight and related development tools, or tools that do things such as embed MS Office documents in web pages.
This principle asserts that Microsoft cannot cause web or application developers to create IE-specific content by default.
me said on April 9th, 2009 at 3:21 am:
David Banes said on April 9th, 2009 at 4:38 am:
Pingback from I’ll keep publishing » Principle 6: Microsoft tools for developing content must not produce IE specific or Windows-specific results. | Mitchell’s Blog
mitchell said on April 9th, 2009 at 7:37 am:
Asa Dotzler said on April 9th, 2009 at 9:43 am:
tsahi said on April 9th, 2009 at 2:42 pm:
Pingback from Mozilla Doesn’t Like the Way Windows 7 Boosts Internet Explorer | google android os blog
dar said on May 19th, 2009 at 7:46 pm:
aski-memnu said on June 2nd, 2009 at 4:33 am:
Pingback from Mozilla Links