Design experience: Can't ignore the compatibility problem of roaming browser

I have to admit, proud tour in the user experience is done better, so its user base is very large. Because of this, some of its bad features also create browser compatibility issues that developers can't ignore.

Flash caching?

Some time ago in the company an internal project, need to embed in the Web page in a batch upload pictures of Flash. This would have been very simple things, in IE, Firefox and other browsers under the test passed, but in a proud tour there is a strange problem: from the second browsing the Web site, flash into a blank. Even if you shut down the so-called Web page acceleration, it is still not normal. After searching with Google, we found that the only solution was to add a bunch of random numbers to the file address to avoid caching.
IE7 or IE8?

Most JavaScript frameworks use Navigator.useragent to determine browser types, such as:
var useragent = Navigator.userAgent.toLowerCase ();
Jquery.browser = {
Version: (Useragent.match (/.+: Rvitraie) [\/:] ([\d.] +)/) [0, ' 0 ']) [1],
Safari:/webkit/.test (useragent),
Opera:/opera/.test (useragent),
MSIE:/msie/.test (useragent) &&!/opera/.test (useragent),
Mozilla:/mozilla/.test (useragent) &&!/(Compatiblewebkit)/.test (useragent)
};

When IE version is 8.0, a "Enable IE8 standard render mode" option appears in the proudly set. If this option is not checked, proud tour defaults to IE7 mode for rendering, useragent in the version of the logo is also IE7:
mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; trident/4.0; SLCC2. NET CLR 2.0.50727;. NET CLR 3.5.30729;. NET CLR 3.0.30729; Media Center PC 6.0; CIBA; MAXTHON 2.0)

Later, I added the x-ua-compatible settings to the page area:

While the Web page is rendered in IE8 mode, the version identified in UserAgent is still IE7.

Proud to swim after the 2.5 version gives me the feeling is getting worse, here look forward to the WebKit core of the 3.0 version.