IE F12 Developer Tool console error message

F12 Developer Tool console error message

This content refers to earlier versions of the F12 tool. Please check the latest F12 tool documentation.

The F12 tool console can report errors and informational messages that occur during runtime. This article describes the error message and provides suggestions on how to fix these errors. Brief Introduction

The F12 tool Console error message provides some code (for example, SEC7111 or HTML1114) that provides information about the error. These codes and messages are displayed in the console and script tabs of the F12 tool. For JavaScript programmers, the code is raised from Windows Internet Explorer. ActiveX and browser extension developers can also send these errors and messages.

The tables later in this topic are divided into sections that include code, messages, descriptions, and recommendations for resolving problems (when applicable). Although the description in this table provides a starting point for debugging issues, the best way to get information is to access the developer forum or Internet Explorer Developer Center Online. Security Error

These errors are in the form of sec7xxx (such as SEC7113). These errors reflect security conditions enforced by Windows Internet Explorer 9, such as mixed content and tracking protection.

Code	message	Description	Suggested Solutions
SEC7111	"HTTPS security is threatened by [name of resource]"	The Secure Hypertext Transfer Protocol (HTTPS) page contains unsafe (mixed) content.	Do not include unsafe content on HTTPS pages.
SEC7112	The script for [URL] is blocked because the MIME type does not match	The HTTP response header for the JavaScript file specified by the URL has a "X-content-type-options:nosniff" header, but no content type declaration.	To add the correct content types for JavaScript files (such as text/javascript, application/javascript, and so on), see the MIME handling changes in Internet Explorer for details and a complete list of content types.
SEC7113	"CSS ignored due to MIME type mismatch"	The imported style sheet was not used because of the wrong MIME type in the HTTP header.	Be sure to pass the style sheet file with the correct HTTP response header that contains the text/CSS content type. For more information, see MIME handling changes in Internet Explorer.
SEC7114	"Downloads in this page have been tracked for protection blocking. [URL provided here] "	The user has used trace protection to block script or content.	None-the user has started.
SEC7115	": Visited and: Link styles are just different colors. Some styles do not apply to: visited. "	Multiple properties, such as font or size, are changed using the visited and link styles.	Change only the color properties.

note for Web sites in security zones that are trusted by the user, Internet Explorer will not check the MIME type of the style sheet. HTML Code

The code is formatted as HTML1XXX (such as HTML1115). They can specify errors or statuses that the developer can control or not control.

Code	message	Description	Suggested Solutions
HTML1112	"Restart from [encoding] to [encoding] code page"	A code page that is different from the server is specified.	Use the same code page as the server to prevent messages from appearing.
HTML1113	Restart the document mode from [mode] to [mode]	The document mode required for a Web page is not the document mode that the browser is currently setting.	This message appears when the user browses from another page, so it is not controlled by the developer.
HTML1114	The code page [codepage] in [domain] replaces the code page in conflict [domain] [codepage]	Specify the conflicting code page in the HTTP headers and tags of the Web site.	Resolves code page conflicts.
HTML1115	"X-ua-compatible META tag ([META tag]") is ignored because document mode is complete	Typically, a "META" tag is placed after the "Script" or "Style" declaration (the document mode that fixed the page).	Move forward the META tags conforming to X-ua as much as possible in the header. It is best to place it immediately after the "<title>" and character set values.
HTML1116	"The META tag conforming to X-ua ([meta tag]") is ignored because of the preceding meta tag ("[Meta tag]") that conforms to the X-ua.	In the "	In addition to leaving a "X-ua META" tag, all other tags are removed and make sure that it is in front of the header as much as possible. It is best to place it immediately after the "<title>" and character set values.
HTML1200	"[domain] is located on the Internet Explorer 9 compatibility View list (' [path to local compatibility View List] '). "	The current Web site is listed on the internal list of Internet Explorer.	Site developers can follow the guide to remove their Web sites from the Compatibility View list. Microsoft regularly updates this list, so these changes can be downloaded and reflected.
HTML1201	"[domain] is the site you added to the compatibility view." "	The user has clicked the Compatibility View button for the current Web site or has added the site through Compatibility View settings.	The user has started.
HTML1202	[domain] is running in Compatibility View because the show Intranet site in Compatibility View is selected. "	User has selected the show Intranet sites in compatibility view check box in Compatibility View settings.	Users need to press ALT + T, click Compatibility View Settings, and then clear the show Intranet sites in Compatibility View check box.
HTML1203	"[domain] has been configured to run in Compatibility View through Group Policy." "	The network administrator has specified that the Web page will run in Compatibility View.	Users need to contact the network administrator.
HTML1204	[domain] is running in Compatibility View because the show all sites in Compatibility View is selected. "	User has selected the Show all Web sites in Compatibility View check box in Compatibility View settings.	Users need to press ALT + T, click Compatibility View Settings, and then clear the Show all Web sites in Compatibility View check box.
HTML1300	"Take a navigation"