发表新帖
发表新帖

WebBrowser component not showing CSS 3

前端 未结
关注
4 1539
别跟我提以往
别跟我提以往 2021-02-06 04:47

I am building a piece of software that requires a WebBrowser component. Unfortunately it won\'t show my page correctly.

My content uses this CSS style:

.
相关标签:
4条回答
  • 误落风尘
    2021-02-06 04:57

    I had the same issue and I changed this line:

    <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />

    to

    <meta http-equiv="X-UA-Compatible" content="IE=11" />

    to the latest verison of IE and it works very well.

    0 讨论(0)
  • 无人共我
    2021-02-06 05:09

    Just for further reference to other people needing this:

    First of all: Thanks to Boo & Lex Li For helping me find the answer to my question.

    You have to set a certain registry to the right value:

    There are two different sets of keys for 32 bit and 64 bit applications.

    32 bit:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION

Value Key: yourapplication.exe

    64 bit:

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION

Value Key: yourapplication.exe

    The value to set this key to is (taken from MSDN here) as decimal values:

    9999 (0x270F)
Internet Explorer 9. Webpages are displayed in IE9 Standards mode, regardless of the  !DOCTYPE directive.

 9000 (0x2328)
 Internet Explorer 9. Webpages containing standards-based !DOCTYPE directives are displayed in IE9 mode.

8888 (0x22B8)
Webpages are displayed in IE8 Standards mode, regardless of the !DOCTYPE directive.

8000 (0x1F40)
Webpages containing standards-based !DOCTYPE directives are displayed in IE8 mode.

7000 (0x1B58)
Webpages containing standards-based !DOCTYPE directives are displayed in IE7 Standards mode.

    Even tough MSDn claims that 9000 is the automatically assigned value. Apperently this is simply not true.

    Below you can find the code how to add these keys to your registry. Please not that your application has a different processname when you debug.

    RegistryKey key = Registry.LocalMachine.OpenSubKey(@"SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION", true);
        if (key != null)
        {
            key.SetValue("YourApplicationName.exe", 9000, RegistryValueKind.DWord);
        }

        key = Registry.LocalMachine.OpenSubKey(@"SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION", true);
        if (key != null)
        {
            key.SetValue("YourApplicationName.exe", 9000, RegistryValueKind.DWord);
        }

    So thanks all and Good Luck

    Edit: User Account Control should be off to make this code work.

    0 讨论(0)
  • 臣服心动
    2021-02-06 05:15

    This page describes how to force the browser control to use a specific render mode.

    You can also try this doctype:

    <!DOCTYPE html>

    And/Or this meta element in the head element:

    <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
    0 讨论(0)
  • 不思量自难忘°
    2021-02-06 05:15

    you can also add a response header to the IIS application Called X-UA-Compatible with a value of IE=Edge. I tend to add it to my web.config

    0 讨论(0)
 看不清?
提交回复
热议问题