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 [url=http://msdn.microsoft.com/en-us/library/ff955275(v=vs.85).aspx]MSDN article about X-UA-Compatibility Meta Tag and HTTP Response Header[/url] 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 [url=http://msdn.microsoft.com/en-us/library/ee330730%28v=vs.85%29.aspx]MSDN: Internet Feature Controls (B..C)[/url] 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 "[i]page looks different in preview and when loaded from the server[/i]", but also could introduce new level of complexity, like - *was registry really updated?* - [i]does my server alter headers differently than my preview environment is set via registry[/i] - [i]isn't my IE configured (eg. via web developers tools) to use different rendering mode than PSPad?[/i] - 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. -- <http://forum.pspad.com/read.php?2,57966,61071> PSPad freeware editor http://www.pspad.com
