Internal Browser

pspad:

did you create whole key or entry only?
did you create it in HKLM or HKCU?

Manually, HKCU (as carbonize posted), both key and entry.

Setting PSPad pref and restarting created nor key nor entry (I searched registry for "FEATURE_BROWSER_EMULATION" and found just entry for silverlight in HKLM.

If I remove the key and try to re-create via PSPad pref, still nothing is created – could it be that NOT setting multi-user environment (my pref) in PSPad prevents ALL registry entries?

Ahh. In this key is list of application with their settings.
I intentionally don't create key if doesn't exists, only add application there.

It will be easy fix - if key doesn't exists I will create it.

Dragging up this old thread to ask if it would be possible to add th eoption to pick which browser to emulate now we are at IE 11.

--
Carbonize

As I know MS, there will be option to use old/new
I know IE10 and above has option to set backward compatibility, but I am not sure, if it is available for engine in the OS.

Just reminding that you can still force internal IE preview to use rendering mode you want 'manually' using explicit document mode inmetaelement.

<meta http-equiv="x-ua-compatible" content="IE=edge" />
<meta http-equiv="x-ua-compatible" content="IE=9" />
<meta http-equiv="x-ua-compatible" content="IE=8" />
<meta http-equiv="x-ua-compatible" content="IE=7" />
<meta http-equiv="x-ua-compatible" content="IE=EmulateIE9" />
<meta http-equiv="x-ua-compatible" content="IE=EmulateIE8" />
<meta http-equiv="x-ua-compatible" content="IE=EmulateIE7" />
<meta http-equiv="x-ua-compatible" content="IE=Chrome=1" />


Most likely the first one will be most usable for you, since it will ensure the newest available engine will be used. Last one is just for completeness, Google Chrome Frame is dying and I am not sure how it would behave in internal preview.

You can include this meta into your\Template\Default.htmland/or (if you haven't done it already) you may extend your\Context\HTML.DEFwith something like
[xua | x-ua-compatible meta ]
<meta http-equiv="X-UA-Compatible" %xua% />
; ... [Macro definition] ...
%xua%=@C x-ua-compatible=,content=,IE=Edge,IE=Edge;IE=9;IE=8;IE=7;IE=5;IE=EmulateIE9;IE=EmulateIE8;IE=EmulateIE7;Chrome=1,"


Edited 1 time(s). Last edit at 2013-08-08 12:30 by myf.

it's no good using x-ua compatiable as you cannot set it to be IE 11 conpatiable if it's et to run in IE 7 mode via the registry. I am talking about updating the registry entry that PSPad creates as based on msdn.microsoft.com

HKEY_CURRENT_USER/SOFTWARE/Microsoft/Internet Explorer/Main/FeatureControl/FEATURE_BROWSER_EMULATION
PSPad.exe = (DWORD)9000

10000 for IE 10 so I'm guessing 11000 will be IE 11 even though it's not officialy out for Windows 7 yet.

--
Carbonize

Edited 1 time(s). Last edit at 2013-08-08 18:04 by carbonize.

I will implement it into PSPad. Thank you for link

carbonize:

it's no good using x-ua compatiable as you cannot set it to be IE 11 conpatiable if it's et to run in IE 7 mode via the registry.

That is new information I was not aware of. From MSDN article about X-UA-Compatibility Meta Tag and HTTP Response Header it seems it should work 'allways'. Are you really sure there were any new gotchas introduced between IE10 and IE11? (I have W7, so cannot test.)

carbonize:

I am talking about updating the registry entry that PSPad creates as based on MSDN: Internet Feature Controls (B..C)

HKEY_CURRENT_USER/SOFTWARE/Microsoft/Internet Explorer/Main/FeatureControl/FEATURE_BROWSER_EMULATION
PSPad.exe = (DWORD)9000

10000 for IE 10 so I'm guessing 11000 will be IE 11 even though it's not officialy out for Windows 7 yet.

Sure, this will be somewhat systematic fix for problem "page looks different in preview and when loaded from the server", but also could introduce new level of complexity, like
- was registry really updated?
- does my server alter headers differently than my preview environment is set via registry
- isn't my IE configured (eg. via web developers tools) to use different rendering mode than PSPad?
- and probably others I overlooked.

What I wanted to remind is that (until PSPad setting works well enough) there is seemingly well documented workaround for the aforementioned problem we can use just now. I didn't want want to explicitly tell that workaround is better.

The registry setting via PSPad works perfectly well for me and means the internal browser will render as the system browser does. I don't believe in adding meta tags just to satisfy a single browser manufacturer when good code will always display correctly.

--
Carbonize