I wonder when Maxthon, Avant, etc. will follow suit?
Neowin Forums > Help & Discussion Center > Software Discussion & Assistance > Web Browser Discussion
So they're packaging IE8 trident in with their release, how is MS happy with that?
If they're just using the system install, then it's a moot issue.
If they're just using the system install, then it's a moot issue.
Quote - (The_Decryptor @ Sep 12 2008, 17:14) 
So they're packaging IE8 trident in with their release, how is MS happy with that?
If they're just using the system install, then it's a moot issue.
If they're just using the system install, then it's a moot issue.
they are using the system install, you have to install IE8beta to get the option to use IE rendering.
The thing is, so far it seems it's the only alternative trident shell doing this. all the other trident shells are still keep using IE7 trident, even if you have an IE8beta installed.
Maxthon is already has IE8 engine support.
Quote - (wellofsouls @ Sep 12 2008, 19:55)
they are using the system install, you have to install IE8beta to get the option to use IE rendering.
The thing is, so far it seems it's the only alternative trident shell doing this. all the other trident shells are still keep using IE7 trident, even if you have an IE8beta installed.
The thing is, so far it seems it's the only alternative trident shell doing this. all the other trident shells are still keep using IE7 trident, even if you have an IE8beta installed.
I think it's probably a API call you need to use to switch into IE8 standards mode, if other shells are still using IE7 behaviour.
Kinda stupid actually (If it's the case), it should behave the same way as normal IE8.
Quote - (iron2000 @ Sep 12 2008, 18:00)
Maxthon is already has IE8 engine support.
nope, Maxthon has "IE8 compatibility", means it no longer acts up weird after you install IE8beta, however it still uses the IE7 engine. Going to Acid2 test (or Acid3 test) clearly shows that.
http://blogs.msdn.com/ie/archive/2008/03/1...des-in-ie8.aspx
It's not an API call, it's a registry key.
:facepalm:
Edit: Apparently you should also be able to do it by calling the CoInternetSetFeatureEnabled function with the FEATURE_NATIVE_DOCUMENT_MODE setting, but whether that works or not is a different matter.
Edit: That was for Beta 1, for Beta 2 it's FEATURE_BROWSER_EMULATION, and the key has changed, http://blogs.msdn.com/ie/archive/2008/08/2...ew.aspx#8903587
It's not an API call, it's a registry key.
:facepalm:
Edit: Apparently you should also be able to do it by calling the CoInternetSetFeatureEnabled function with the FEATURE_NATIVE_DOCUMENT_MODE setting, but whether that works or not is a different matter.
Edit: That was for Beta 1, for Beta 2 it's FEATURE_BROWSER_EMULATION, and the key has changed, http://blogs.msdn.com/ie/archive/2008/08/2...ew.aspx#8903587
Quote - (The_Decryptor @ Sep 12 2008, 18:17)
I think it's probably a API call you need to use to switch into IE8 standards mode, if other shells are still using IE7 behaviour.
Kinda stupid actually (If it's the case), it should behave the same way as normal IE8.
Kinda stupid actually (If it's the case), it should behave the same way as normal IE8.
Quote - (The_Decryptor @ Sep 12 2008, 18:52)
http://blogs.msdn.com/ie/archive/2008/03/1...des-in-ie8.aspx
It's not an API call, it's a registry key.
:facepalm:
Edit: Apparently you should also be able to do it by calling the CoInternetSetFeatureEnabled function with the FEATURE_NATIVE_DOCUMENT_MODE setting, but whether that works or not is a different matter.
Edit: That was for Beta 1, for Beta 2 it's FEATURE_BROWSER_EMULATION, and the key has changed, http://blogs.msdn.com/ie/archive/2008/08/2...ew.aspx#8903587
It's not an API call, it's a registry key.
:facepalm:
Edit: Apparently you should also be able to do it by calling the CoInternetSetFeatureEnabled function with the FEATURE_NATIVE_DOCUMENT_MODE setting, but whether that works or not is a different matter.
Edit: That was for Beta 1, for Beta 2 it's FEATURE_BROWSER_EMULATION, and the key has changed, http://blogs.msdn.com/ie/archive/2008/08/2...ew.aspx#8903587
Actually, I don't think it's that complicated. I don't think it has anything to do with API calls or registry keys to change the IE8 trident rendering mode, but rather the other IE shells are just still not picking up the new IE8 trident engine. So they are still keep using windows/ie7/mshtml.dll instead of switching to windows/ie8/mshtml.dll thus they are still using the old IE7 trident instead of the new IE8 beta trident.
Unless they're packaging their own version, then they're using the system version (i.e. IE7, IE8, etc.)
Quote - (The_Decryptor @ Sep 13 2008, 01:15)
Unless they're packaging their own version, then they're using the system version (i.e. IE7, IE8, etc.)
well, IE8 beta installation doesn't overwrite IE7, so the IE7 mshtml.dll is still there, and you can change the browser mode to IE7 mode (not IE8 compatibility mode) with IE8b2's Developer Tools. I guess the other trident shell just don't want to switch to IE8 mshtml.dll because that means they have to implement the extra features of switching modes.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.