We are having HTML Launch page with various control like dropdownlist box, text box, report frame which is running on webfocus 7.6.11 version.

we are trying to call this launch page from the parent application (not in webfocus) within iframe.

everything is working fine in Chrome, Firefox.

Only in Internet explore its having error even in IE its working fine with IE5 engine.

I am trying to override the frame engine using

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

but its not accepting

I cannot change the parent page as it need to run on edge mode.

error i am getting is
Object doesn't support property or method 'evaluate'
in ibirls3.js


Any suggestion will be highly appreciated

This message has been edited. Last edited by: krish,

You will need to find out which object the evaluate method is expected to be on.

My guess is that the object is null.

Thanks for the response, problem is IE 11 will not support evaluate method. we need some fix particular to IE like below but I am trying to avoid change in ibirls.js as its part of product.

if(window.DOMParser)
            {
                result =
                    root
                        .evaluate(
                            expression,
                            node,
                            null, 
                            XPathResult.ANY_TYPE,
                            null);
            }
            else // Internet Explorer
            {
                result = node.selectNodes(expression);
            }
			

Thanks
Krishnan

I think you need to work out what object the evaluate is being called on, this will give you an idea where the issue is being caused.

The only other suggestion I have would be to contact Tech Support

I am already working with tech support, I thought if someone faced the similar issue and resolved the same it would save some time.

code which is having problem is which is from ibirls3.js

if(isIEvar)
	{
	   node = xmlNode.selectSingleNode(nodeName);
	}
	else
	{
	    var owner = xmlNode.nodeType == 9 ? xmlNode : xmlNode.ownerDocument;
        var xpathResult = owner.evaluate(nodeName, xmlNode, null, 0, null);
        node = xpathResult.iterateNext();
   }

Well, hopefully someone else on the forum has experienced this.

Usually when this sort of thing happens, there is something that has broken or no populated as expected and the IBI JS files can't handle it.

Thats why I was suggesting tracking the issue back to the source.

Thanks Waz, IBI tech is saying as long as we are getting the report in the browser with no errors they are good.



now I am little bit worried, as I am able to reproduce the issue with IE11 edge mode.
I am checking back with them.

I think it's something to do with forcing the iframe to use different engine(IE 5) or make the report page work in edge mode in IE will the solution.

Edge is a new IE and I don't think that IB have certified WF with it yet.

We are considering rolling out IE11 during our upgrade from 7705 to 8103. IE11 is not playing nicely with 7705 even with enterprise mode enabled. So far we have found that InfoAssist Define and Compute windows will not allow selection of field names by double click or drag and drop. They would have to be typed in and this will be a pain to the non-coders. There were a few other minor things that I don't have in hand right now. So we will probably have to hold IE11 until post-golive.

I don't think that IE11 is certified for use with WF7.7.05.

T

is this evaluate() method an IBI API or javascript method? The correct javascript method should be eval().

I think Evaluate() is an java script, which will work in other browser(Chorme, Firefox) except IE

We have all kinds of IE issues and it's not because of IE11, it's because IBI forces specific versions with the "X-UA-Compatible" meta tag, that can't be overwritten. Their code doesn't support higher versions of IE which is why it's there. We have a ticket open and have had them fix an IE issue, which came out in 8.1.05, that was forcing IE 10 when using portals, yet, we are still having issues, because their fix is very flaky. There is no override for their meta tag and if you go into IE, hit F12, go into the Emulation tab, then select document mode to a higher version, you will most likely, see it works. Personally, I use Chrome as well does 60% of the world. IE holds 6% so I tend to say, "move to Chrome".

Since I've began developing portals and content in 8.1.xx, I've been developing everything so that it works well in Chrome first and foremost. Why? Because IE is on its deathbed and nothing developed tends to run smoothly or look decent in IE. Firefox offsets my custom HTML widgets I create so they aren't centered in panels, but other than that things work a lot better than in IE. In Chrome, everything works, and does so quickly. Thus, for now, anything created with IBI products is being developed for Chrome since IBI doesn't want to get with the times and make things browser agnostic. I wish content we create with IBI products worked without issue and workarounds in all 4 major browsers. But that is I guess asking too much of them.

Issue got resolved by enabling the Enterprise mode in IE.

Thanks all for your input.

I have the same problem - I get the JS error "Object doesn't support property or method 'evaluate'" when running a page created in Dev Studio 7.7.03 or 7.7.05 - we are WF 8.0.08 and IE11. I can resolve the issue by opening and saving the page in Dev Studio 8.0.08. We're forbidden to look at code but a bunch of stuff gets updated in the html meta tags and I cannot trace which exact line will resolve the issue.

quote:

We're forbidden to look at code

First option:
After you build your HTML page in AS, open in external editor, copy the code, paste it into a FEX and wrap -HTMLFORM BEGIN/END around it. Works exactly the same, but you are able to view and edit the code any time you like.

Second option:
I've also found, I can rename the file through properties to TXT. Then in AS just say OPEN file, it notices that it's really a TXT and lets you edit the text. Even though the tree doesn't refresh, showing it's a TXT. Just remember to rename it back.

You're lucky to be on 8.1.04, where apparently the first really usable version of App Studio exists. We're on 8.0.08 where Dev Studio is the only reliable tool. App Studio I won't touch.

I started using AS just this week. Mainly, because at some point, I'm not going to have a choice. However, it is said by IBI, who was here in our office this week, that DS will be supported until AS has everything DS has. I know that isn't true, but I responded with, so DS will always be supported, since David refuses to put, "Open in Text Editor" for HTML files, which DS does today. A few of the IBI reps looked at each other and said, "good point". Though I have a work around, I'm sure they will work hard on closing up that gap.

Personally, I don't use the HTML Composer for either DS or AS. I end up building my own HTML5 pages and pulling reports or graphs I build using InfoAssist into them. DS and AS both write code specific to browsers and pull in so much crap that isn't needed, it's a nightmare to fix when something goes wrong between WF versions. Which is why I hate the aspect of not being able to edit my own HTML files in AS.

David is so focused on thinking everyone using WF also uses their HTML Composer, without the possibility of a developer actually doing what I'm doing, he hasn't noticed people that do web development are not only Business Analysis. Which personally, I think he is, which is why he doesn't understand our needs.

Hi Francis,
Glad that you also got this same issue . Is any one have feasible solution so that 7.6.11 HTML page will work on IE 11 EDGE mode.

without enabling Enterprise mode.

If the web page is referenced in a B.I. Portal page, setting the X-UA-Compatible meta header to edge or 9 doesn't make any difference, because BIP sets it to 10.

<!DOCTYPE html>

<html>
	<head>
	    <title>BI Portal</title>
		<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
		<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE10" >		
		<meta http-equiv="MsThemeCompatible" content="yes">
		<meta http-equiv="ImageToolBar" content="no">
		<link type="text/css" rel="StyleSheet" href="/ibi_apps/bindows/css/bimain.css">
		<script type="text/javascript" src="/ibi_apps/bindows/js/application.js"></script>
	</head>
	<body>
		<script type="text/javascript">application.start("/ibi_apps/bindows", "/ibi_apps/tools/portal/resources/markup/wfbiportalrun.jsp?&ViewID=VR-IGV5ZELR1XVE1Z32J526&ViewName=ie11_test&ViewTitle=ie11_test&SessionTimeout=7200000")</script>
	</body>
</html>

I found an interesting fact today. You would think IBI would use metatag to force compatibility because of code limitations they might have. Open the same portal up that says it emulates IE10, in Chrome or firefox. It says it emulates IE8.

Some smart developer over in IBI, is setting the IE Compatible mode differently, based on the browser that is accessing it. Guess they didn't realize that that setting is for IE only and everyone else ignores it.

Ha ha



Welcome
To
Focus

Welcome
To
Focalpoint

haha.. Nice..

I was going to respond with "Wait To ****", if someone asked.. :P


Edit: really, they * out F-A-R-T