I have Recorded Coded UI Test With Silverlight 5 Application With IE Browser. but when i am trying to Run it for Chrome it's not working.
For non silverlight application it is working fine.
I have installed Cross Browser plugin for chrome.
As per my comment, Cross browser testing is only for web applications. Silverlight testing is not supported in Chrome or Firefox.
Since Silverlight is a browser plug in, if something works in Silverlight/IE then you can rely on it working in FF and Chrome. If it fails then it's a problem with Silverlight, not your application.
Related
Does anyone know if it's possible for a Chrome extension to interact with a PWA? Since a PWA installed by Chrome seems to be just a Chrome wrapper for the web application, perhaps Google still allows extensions to interact with the PWA.
I know you can work with beacons with a iOS app or Android app.
But you can work with a web app to?
(A website recognize a beacon and do something)
Unfortunately, the general answer is no. You need native components to detect Bluetooth beacons on both Android and iOS. The web browsers on both operating systems have no hooks to detect beacons via JavaScript or HTML.
Chrome OS does have Bluetooth bindings in its Chrome browser, which may allow you to build a web app on Chrome OS that does this. But this would really be a Chrome App not a general purpose web app.
The Chrome browser for iOS and Android also detects Eddystone-URL beacons, but it will not pass the detection info to a web app. Detections are sent to the user as a notification and tapping on that notification simply brings up a configured URL in the Chrome web browser. This does not allow any dynamic web app behavior based on beacon detections.
Till now I have been using the default browser with my Samsung Galaxy S2. When Browsing if I found and clicked on a link that was from Wikipedia or IMDB for instance it would ask and give the choice if I wanted to open them in the "Internet" Browser or the installed IMDB/Wikipedia App. I have since tried other Browser Apps. (Firefox, Dolphin, Skyfire, Opera etc) and none of these appear to pop up with the option to open them in an app. They go straight to the website. The only app I have found that does offer the choice is Chrome, but it seems to crash a bit too often. Am just wondering if I am missing something in the the other browsers I have looked at. I like Dolphin and Firefox, but would like to see them offer the option to open sites in installed apps. Is there options to get them to do this? Thanks!
It is because those browsers (Firefox, Dolphin, Skyfire, Opera) you have tested at the end of 2012 don't support or have problems with calling external intents.
Here is the issue about implementation that feature on Firefox.
Related information - how to use intent filters to open external Android app from browser.
We are developing an app with Sencha Touch 2 and PhoneGap 2.0. We also want to use WebGL.
But neither the android browser nor safari mobile supports it.
However Opera Mobile 12 supports WebGL. Is it possible to start the sencha app with Opera Mobile?
Firstly, PhoneGap overrides the capability of Native Android browser. We cannot use the Opera Mobile browser features for developing the PhoneGap Applications.
Secondly, Sencha Touch is not supported by Opera Mobile. It runs only on WebKit browsers. I am not sure about Mobile chrome. But any other browser except android default browser will not able to run all features of sencha.
Hope you got your answer.
You can try RhoElements v1 browser. It also only supports WebKit as far as I know.
https://docs.symbol.com/ReleaseNotes/RE_0100001000_ReleaseNotes.html
http://www.spritle.com/blogs/2012/01/04/rhodes-3-3-x-supports-motorola-rhoelements-and-android-et1/
I recently developed a web app which used the JavaScript window.location property to redirect the browser. This worked fine on PC browsers, but did not function at all on both of the Android browsers I tried it on.
The unsupported browsers were: Browser (built-in) and Dolphin Browser.
I discovered that location.replace() does work on these browsers, as well as on the PC.
Is this Android limitation documented anywhere, and what other redirect methods are available on the Android platform?
PHP redirects seem to work fine in the Dolphin browser HD.
For raw JavaScript redirect, location.replace() works.
The more robust way of redirecting would be to use JQuery, as this should handle platform-specific cases under the covers.