At the needs of Vietnamese customers yesterday, add a map for them and use the map provided by the Vietnamese themselves.VietbandoMap:
API: http://vietbando.vn/api/examplesE.aspx
When the project is introduced, a parameter error is always reported. After an afternoon, I was puzzled. I had no way to exclude them one by one. After that, I changed <HTML...> to <HTML>.
Hey !!!! Really despise them.
TIPS:
Writing interfaces must be standardized. Otherwise, when developing interfaces based on others, I really want to beat you !!
Solution:
X-UA-compatibleThis is a newly added setting for IE8. browsers other than IE8 do not recognize this. The difference between this setting and content = "Ie = 7" regardless of whether the page contains <! Doctype> commands all use the standard mode of Windows Internet Explorer 7. The content = "Ie = emulateie7" Mode follows <! Doctype> command. For most websites, it is the preferred compatibility model.
Currently, IE8 is still in the beta version. To avoid page errors under IE8, we recommend that you use IE7 for rendering. That is, directly Add the following code to the meta tag of the header on the page:
- <meta http-equiv="X-UA-Compatible" content="IE=7" />
In this way, we can make the page behave normally in IE8!
<! DOCTYPE html PUBLIC "-// W3C // dtd xhtml 1.0 Transitional // EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
- <HTML xmlns = "http://www.w3.org/1999/xhtml">
- <Head>
- <Meta http-equiv = "Content-Type" content = "text/html; charset = UTF-8"/>
- <Meta http-equiv = "content-language" content = "UTF-8"/>
- <Meta http-equiv = "X-UA-compatible" content = "Ie = 7"/>
- <Meta http-equiv = "Pragma" content = "no-Cache"/>
- <Meta content = "Focus on web standards, user experience, front-end technologies, web designers, front-end development engineers, liupeng, Beijing China" name = "keywords"/>
- <Meta content = "Focus on web standards, user experience, front-end technologies, web designers, front-end development engineers, liupeng, Beijing China" name = "Description"/>
- <Meta content = "sablog" name = "Copyright"/>
There is one more sentence in it.
- <meta http-equiv="X-UA-Compatible" content="IE=7" />
X-UA-compatibleWhat is it?
Let's take a look at the description on msdn:
In IE8 Beta 1, that option is the "IE = 7" X-UA-Compatible tag, which instructs IE8 to display content in IE7 Standards mode. however, the scenario this doesn't address is when IE = 7 is applied as an HTTP header to a site that contains Quirks mode pages. the IE = 7 HTTP header will force all pages-both Quirks and Standards-to display in IE7 Standards mode. developers using this header while updating their sites wocould then have to add the "IE = 5" <META> tag to each page they want to keep in Quirks mode. this logic is fine for processing websites. however, if a site has lots of Quirks mode pages, or for the case where pages with frames host a mix of Strict and Quirks mode content-as brought to light by IE8 Beta 1 user feedback-the compatibility opt-out adds a bit more work we intended.
I will summarize the following content:
X-UA-compatibleThis is a newly added setting for IE8. browsers other than IE8 do not recognize this. The difference between this setting and content = "Ie = 7" regardless of whether the page contains <! Doctype> commands all use the standard mode of Windows Internet Explorer 7. The content = "Ie = emulateie7" Mode follows <! Doctype> command. For most websites, it is the preferred compatibility model.
Currently, IE8 is still in the beta version. To avoid page errors under IE8, we recommend that you use IE7 for rendering. That is, directly Add the following code to the meta tag of the header on the page:
- <meta http-equiv="X-UA-Compatible" content="IE=7" />
In this way, we can make the page behave normally in IE8!
Reference: introducing Ie = emulateie7