F12 Developer Tools Console error message

F12 Developer Tools console error message12 out of 17 rated this helpful-rate this topic

This content references an earlier version of the F12 tool. Please see the latest F12 tool documentation.

The F12 tool console can report errors and informational messages that occur during runtime. This article describes the error messages and provides suggestions on how to fix them. 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, this 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, where applicable, recommendations to resolve the issue. Although the description in the table provides a starting point for problem debugging, the best way to get information is to visit the Developer forum or the Internet Explorer Dev Center online. Security Error

These errors are formatted as SEC7XXX (for example, SEC7113). These errors reflect security conditions enforced by Windows Internet Explorer 9, such as mixed content and trace 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	"[URL] script is blocked because of mime type mismatch"	The HTTP response header for the JavaScript file specified by the URL has a "X-content-type-options:nosniff" header, but there is no content type declaration.	To add the correct content types for JavaScript files (such as text/javascript, application/javascript, and so on), see MIME processing changes in Internet Explorer for a complete list of details and content types.
SEC7113	"Ignore CSS due to MIME type mismatch"	The imported style sheet was not used because of an error MIME type in the HTTP header.	Ensure that the style sheet file is passed with the correct HTTP response header that contains the text/CSS content type. For more information, see MIME processing changes in Internet Explorer.
SEC7114	"The download in this page has been blocked by tracking protection. [URL provided here] "	The user has used tracking protection to block scripts 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, have been changed using the visited and link styles.	Change only the color properties.

Note Internet Explorer does not check the MIME type of the style sheet for sites in the security zone that the user trusts. HTML Code

The format for these codes is html1xxx (such as HTML1115). They can specify errors or states that the developer can control or not control.

Code	message	Description	Suggested Solutions
HTML1112	"Start again from [encoding] to [encoding] code page"	A code page that differs from the server is specified.	Use the same code page as the server to avoid the occurrence of messages.
HTML1113	Start the document mode from [mode] to [mode] again	The document mode that the Web page requires is not the document mode currently set by the browser.	The message appears when the user browses from another page, so it can be controlled by the developer.
HTML1114	[Domain] code page [codepage] replaces the code page in the conflicting [domain] [codepage]	Specifies the conflicting code page in the HTTP header and markup for the Web site.	Resolves code page conflicts.
HTML1115	"The x-ua-compatible meta tag was ignored (" [Meta tag] ") because the document mode was completed"	Typically, the "META" tag is placed after the "Script" or "Style" declaration (the document mode in which the page is pinned).	Move the META tag that meets X-ua in the header as much as possible forward. It is best to place it immediately after the "<title>" and the character set values.
HTML1116	"META tag conforming to X-ua (" [Meta tag] ") is ignored because of the META tag (" [Meta tag] ") that precedes X-ua"	In the "	In addition to leaving a "META-compliant X-ua" tag, all other tags are removed and make sure that it is as far as possible before the header. It is best to place it immediately after the "<title>" and the 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 guidelines to remove their sites from the Compatibility View list. Microsoft regularly updates this list, so these changes are downloadable and reflected.
HTML1201	"[Domain] is a website that you add to 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 Intranet sites in Compatibility View is selected." "	The 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.	The user needs to contact the network administrator.
HTML1204	"[domain] is running in Compatibility View because" show all sites in Compatibility View "is selected. "	The user has selected the show all 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 sites in Compatibility View check box.