Editing Internet Explorer (section)

===Non-standard extensions===
Internet Explorer has introduced an array of proprietary extensions to many of the standards, including HTML, CSS, and the DOM. This has resulted in several web pages that appear broken in standards-compliant web browsers and has introduced the need for a "quirks mode" to allow for rendering improper elements meant for Internet Explorer in these other browsers.

Internet Explorer has introduced several extensions to the DOM that have been adopted by other browsers.

These include the inner HTML property, which provides access to the HTML string within an element, which was part of IE 5 and was standardized as part of HTML 5 roughly 15 years later after all other browsers implemented it for compatibility,<ref>{{Cite web|url=https://www.xul.fr/en/html5/innerhtml.php|title=innerHTML and compatibility|website=www.xul.fr}}</ref> the XMLHttpRequest object, which allows the sending of HTTP request and receiving of HTTP response, and may be used to perform [[AJAX]], and the designMode attribute of the content Document object, which enables rich text editing of HTML documents.{{Citation needed|date=December 2011}} Some of these functionalities were not possible until the introduction of the W3C DOM methods. Its [[Ruby character]] extension to HTML is also accepted as a module in W3C XHTML 1.1, though it is not found in all versions of W3C HTML.

Microsoft submitted several other features of IE for consideration by the W3C for standardization. These include the 'behavior' CSS property, which connects the HTML elements with JScript behaviors (known as HTML Components, HTC), [[HTMLplusTIME|HTML+TIME]] profile, which adds timing and media synchronization support to HTML documents (similar to the W3C [[XHTMLplusSMIL|XHTML+SMIL]]), and the [[Vector Markup Language|VML]] [[vector graphics]] file format. However, all were rejected, at least in their original forms; VML was subsequently combined with [[PGML]] (proposed by [[Adobe Systems|Adobe]] and [[Sun Microsystems|Sun]]), resulting in the W3C-approved SVG format, one of the few vector image formats being used on the web, which IE did not support until version 9.<ref>{{cite web|url=http://www.codedread.com/svg-support.php|title=SVG Support Tables|last=Schiller|first=Jeff|work=codedread.com|access-date=April 20, 2019}}</ref>

Other non-standard behaviors include: support for vertical text, but in a syntax different from W3C CSS3 candidate recommendation, support for a variety of image effects<ref>{{cite web |url=http://webfx.eae.net/tools/filtertool.html |title=Filter Tool (WebFX) |date=May 12, 2005 |publisher=webfx.eae.net |access-date=October 4, 2008 |archive-date=October 16, 2010 |archive-url=https://web.archive.org/web/20101016072244/http://webfx.eae.net/tools/filtertool.html |url-status=dead }}</ref> and page transitions, which are not found in W3C CSS, support for [[obfuscated code|obfuscated]] script code, in particular [[JScript.Encode]],<ref>{{cite web|url=https://docs.microsoft.com/en-us/previous-versions//cbfz3598(v=vs.85)|title=Using Script Encoder|date=October 24, 2011|work=Microsoft Docs|publisher=[[Microsoft]]|access-date=April 20, 2019}}</ref> as well as support for [[font embedding|embedding]] [[Embedded OpenType|EOT]] fonts in [[Font embedding on the Web|web pages]].<ref>{{cite web|url=https://www.microsoft.com/typography/web/embedding/default.aspx|title=Font Embedding for the Web|date=February 26, 2001|work=Microsoft Typography|publisher=[[Microsoft]]|archive-url=https://web.archive.org/web/20050428064515/http://www.microsoft.com/typography/web/embedding/default.aspx|archive-date=April 28, 2005|access-date=April 20, 2019}}</ref>