Correct, although you might want to double-check that you didn't accidentally enable it, because if it's enabled and you view it from a web server then I think you will get parts of the screen blank.commit wrote:So i think MOTW option cannot be used.
You cannot expect that?commit wrote:I will check the IE settings but as Ramon said we cannot expect the customer to change the IE settings.
Yes, I'd try that. I am not disagreeing with you, but given how difficult it is these times to bring on new users and retain existing ones I don't think it is smart to point to the requirements and slam the receiver on the hook. XP is still supported by Microsoft and that should be the general rule as to which OS an app should support.i-tietz wrote:If you say in your software requirement list that for the software Windows 7 is necessary and a customer calls and tells you he wants to work with it under Windows XP, what would you say? Are you trying to tell me, you would try to make it work under XP?
My point is not, whether MS is supporting something, but what you developed the software for.RamonS wrote:XP is still supported by Microsoft and that should be the general rule as to which OS an app should support
: And you have the same problem regardless if you launch the help manually or launch it from your application?commit wrote:The issue is only with IE as the help is working perfectly in other browsers.
If the context sensitive help works fine then it implies it's how you're calling the whole application that might be the problem. How is that call structured? Is it pointing to Default.htm, which it should if you're calling to the whole help, or is it calling to Default_CSH.htm, which you'd only use if you're making a CSH call?commit wrote:The issue is only with launching the whole webhelp in the application.
Firefox and Chrome might be compensating for something that IE can't. For example, perhaps the "welcome" topic was originally titled HelpWelcome.htm and you renamed it to helpWelcome.htm and the target or skin or whatever for some reason didn't recognize the name change. In that case you'd have to reselect the welcome file in the target or skin and rebuild to see if that worked in IE. Don't know if that situation is valid, but checking the welcome page is one thing to eliminate.commit wrote:As per my understanding if the issue is with how the webhelp is being called in that case it should not be launched in Firefox and Chrome also. But that is not the case. The whole webhelp is launched perfectly in these browsers.
And the appliction still works when the help is open?LindaW wrote:So, I was able to find a JavaScript routine that turns Compatibility mode off - temporarily - when a page in WebHelp opens, and turns it back on when it closes. I put the Script on the Master Page, so that it is turned on and off for each page.
