TestComplete - ObjectSpy could not identify objects in Windows Vista/Windows 8 - testcomplete

I am using TestComplete 9.3. In Windows Vista/Windows 8, when I try to access object details using ObjectSpy, I can select only outer frame of an application and not the specific element in the UI. Somehow, the other elements do not appear.
But in Windows 2K8, I can identify all the objects using ObjectSpy. Is there any setting that needs to be done for Windows Vista/Windows 8?
Please assist on the same.

As a rule, testing web application requires installing Chrome of Firefox patches (depending on what browser you are using) in TestComplete. Please refer to the following pages to find the patches, as well as to learn the browser versions that are supported by TestComplete 9.30:
Firefox patches: http://support.smartbear.com/downloads/testcomplete/firefox-patches/
Chrome patches: http://support.smartbear.com/downloads/testcomplete/chrome-patches/

Related

Share screen of Microsoft Windows 10 apps using webrtc

When a Windows 10 computer wants to share some of its screens using webrtc protocol (firefox navigator), a list of the windows that can be shared appears. In this list, only "normal" applications appears, not the one related to "apps". By example, spotify window appears, but OneNote window is not listed.
It seems (?) webrtc screen share is not compatible with UWP apps.
Knows someone a way to share the screen of an app via webrtc ?
Note: following link allows to reproduce this issue:
https://mozilla.github.io/webrtc-landing/gum_test.html
you do not need share anything, just push "window" and see the list of windows that appears.
I believe Chromium (the open source version - not sure about Chrome) faces the same problem as UWP requires to use a new Win 10 API which shows it's own window selector. And then obviously that selector doesn't work on other problems. So it's a common problem on Win 10, with no known good solution as far as I can tell.

Windows 10 WebView and Adobe Flash

The new Microsoft Edge browser has built-in support for Adobe Flash. The updated WebView control in the Windows 10 SDK utilizes Microsoft Edge as its engine.
I am trying to figure out how to enable the WebView control to render Adobe Flash content from a website in a Universal Windows App (either a Hosted Web App or a Packaged Web App).
Any ideas or pointers would be much appreciated.
Thanks.
WebView doesn't use Edge as the engine but uses IE11. Quote from the docs - "WebView always uses Internet Explorer 11 in document mode".
It also doesn't support any plugins or such, which would include Flash.
Full run of caveats from the control doc:
It does not support any ActiveX controls or plugins like Microsoft
Silverlight or Portable Document Format (PDF) files. Additionally,
WebView does not support some HTML5 features including AppCache,
IndexedDB, programmatic access to the Clipboard, and geolocation.
More "tidbit" reading up at https://msdn.microsoft.com/en-us/library/windows/apps/windows.ui.xaml.controls.webview.aspx .
Enjoy. Hope this helps. Healy in Tampa.
On Universal application, the webview is using edge now but it does not change anything regarding plugins.
Here is what it says from the MSDN :
In apps compiled for Windows 10, WebView uses the Microsoft Edge
rendering engine to display HTML content. In apps compiled for Windows
8 or Windows 8.1, WebView uses Internet Explorer 11 in document mode.
It does not support any ActiveX controls or plugins like Microsoft
Silverlight or Portable Document Format (PDF) files.

How to get ActiveX recognised as add-on and allowed to run in IE11

Our web browser plugin has worked in all IE versions and still works fine in IE9 and IE10 but in IE11 the plugin is not even recognized and listed as an add-on. It's as if IE11 no longer supports ActiveX.
NOTE: this questions is asked as the developer of the plugin and not the end-user who might need to correct IE settings. So suggestions for how to detect ActiveX or how to adjust a browser settings to allow ActiveX are useless here.
We assume that what we need to do is make adjustments to the ActiveX structure so that IE11 on Windows 8 approves the plugin so that it can be available to the user at their discretion, ie: list it in the Add-on Manager.
A sample project and test page can be downloaded from here - http://addmine.com/temp/EPM_project.zip
Surely there is a workaround but what do we need to change?
As of IE11, add-ons are supported only for IE on the desktop. If you're running the Windows Store experience of IE, then your statement about IE11 not recognizing the plug-in is absolutely correct. This article shows how you can have this experience prompt the user to open the page in the desktop experience of IE, which will support your plugin.
Having said that, it's entirely possible that you do change your plugin to support changes to the Windows 8 security model. Here are a couple of links to get you started:
Supporting enhanced protected mode (Note that this is part 1 of a four-part series)
IEInternals: Understanding Enhanced Protected Mode
IE Blog: Enhanced protected mode
Hope this helps...
-- Lance

Scripting disabled in WebBrowser control?

I have a VB6 application using the WebBrowser control. It displays HTML pages from a local folder (using file:// URI scheme). Some of those pages contain embedded JavaScript code.
It all works well for the vast majority of users, but occasionally we get reports from people who have problems with everything JavaScript-related in the pages. Basically, it looks like they have scripting disabled inside the WebBrowser control.
The problem is: I cannot even reproduce the problem. I was trying to fiddle with various settings in IE security (IE8 on Win XP Pro SP3), disabling various scripting-related options for different zones (which zone includes local file system, by the way?), - I'm always having JavaScript running well in my tests.
Does anybody have any idea of what may be going wrong?
Thanks
I think I know why this is happening, it's because the IE version the WebBrowser control renders under is IE 7.0 in most, and if they are using a browser older than IE 7, it will render under IE 4.0 (seriously). They do this for backwards compatibility. So if some of your users have IE 6, their default IE rendering engine will be IE 4.0. Of course, since you are probably using IE 9, yors would be IE 7 engine.
You can change the engine, if this is what you want to do, to the current engine (ie: to the current version of internet explorer installed on the users system).
Also, I'd like you to go to http://whatsmyuseragent.com/ on your IE browser, and then through the hosted WebBrowser control; you'll see the difference.
Also, ask your problemed users to go to http://whatsmyuseragent.com/ through their hosted WebBrowser control if they can, and note the results, if they are running pre-IE-7 then most likely their hosted webbrowser control will show IE 4.0. This is almost certainly the reason for your problem.

Is TWebBrowser dependant on IE version?

I am thinking about using the TWebBrowser component that comes within Delphi's default pallet of components in a project, but I wonder if it uses the IE version installed on the client machine?
If yes:
then I guess it would share its history, cookies, workoffline and stuff like that?
Can I separate them somehow?
Is there any webbrowser component that is free and is not shared with Internet Explorer on the client?
The current answer is not quite correct. It appears for compatibility purposes, the WebBrowser control will run in IE7 Standards Mode by default unless you add some registry settings.
See:
WebBrowser Control Rendering Modes in IE8 (archive)
More IE8 Extensibility Improvements (archive)
So it's not quite the current IE version. You can also check this if you use fiddler or check the web server logs for the agent string - as it alters the agent string used too!
Yes, TWebBrowser uses whatever IE version is installed on the machine.
Take a look at this similar thread for some possible alternatives..
How to embed a browser object, other than IE<n>, in a Delphi application
Yes, TWebBrowser is tied to Internet Explorer. If you want a standalone HTML viewer, then look at the PBear components.
TWebBrowser is a wrapper around IE ActiveX interface.
So, in the end,
TWebBrowser = Internet Explorer

Resources