I'm using Eclipse Luna and I have created an app using the Google App Engine SDK.
When I'm trying to deploy my app to GAE, Sign in to Google Services window open and when I give my Google credentials it show another window with Account Permissions. But I can't click Accept and Cancel buttons in this window, because this window display that page using Internet Explorer embedded window. Due to issues in IE, those buttons are disabled.
So I change my browser from Window => Preferences => General => Web Browser to Firefox. But still Sign in to Google Services window is open in IE embedded window.
How can I change this to open in Firefox embedded window?
I think answer is update your IE7 , 8 to IE9.. it will work fine.
It's not possible to change the embedded browser in Eclipse. There is a very old bug open to add this functionality, but it doesn't look promising. See also this answer.
For now the solution is to to use an external browser, as was suggested above.
Related
I have Chrome installing my PWA on Android - once it's installed I'd like to automatically close the browser window it was installed from, and open the PWA (so the user doesn't continue in the browser window, thinking they're using the PWA) - is this possible?
i was looking for a similar solution and have not yet found a way to do that. I try to describe my findings so far:
CLOSING THE BROWSER WINDOW:
as described in this answer window.close() can only be called on windows/tabs that the script opened itself. Some possible workarounds are being discussed there.
OPENING THE PWA RIGHT AFTER INSTALLATION:
Google describes in their WebApk Fundamentals Article it as follows:
When a Progressive Web App is installed on Android, it will register a set of intent filters for all URLs within the scope of the app. When a user clicks on a link that is within the scope of the app, the app will be opened, rather than opening within a browser tab.
I was hoping that would work also right after the installation/Adding to homescreen from the still open browser window.
Based on testing with two Android devices it seems as if at the moment the user has to manually open the PWA from the homescreen once for chrome/android to interpret the scope of the web apps manifest.json as intend to open the page in standalone.
This is sad for even iOS seems to handle that different.
Maybe I am overlooking something in the Google Article? I also do not fully understand androids intent API - so maybe there is some way to still achieve that (?)
Based from this blog post:
When the PWA is installed, it will appear in the home screen, in the
app launcher, in Settings and as any other first-class citizen app in
the OS, including information on battery and space used in the system.
There's a tracking event when the user opens the app from the home screen. That means the user has clicked the app's icon or, on Android with WebAPK support, also clicked on a link pointing to the PWA scope and need to close the browser.
start_url: '/?utm_source=standalone&utm_medium=pwa'
Also, the following script leaves us a boolean stating if the user is currently in a browser (true) or a standalone app mode (false)
var isPWAinBrowser = true;
// replace standalone with fullscreen or minimal-ui according to your manifest
if (matchMedia('(display-mode: standalone)').matches) {
// Android and iOS 11.3+
isPWAinBrowser = false;
} else if ('standalone' in navigator) {
// useful for iOS < 11.3
isPWAinBrowser = !navigator.standalone;
}
I had this problem on Android with Chrome. The change that made the difference is adding "target='_blank'" to the link. It looks like:
window.addEventListener('appinstalled', function(event){
setTimeout(function(){
presentToUser("<a href='https://myhostname.com' target='_blank'>Go to App</a>")
}, 10000)}
});
The ten second timeout is to give Android the time to set up the App on the home page.
I had made that adjustment earlier; possibly I can remove it?
But setting the target was what made this work.
The App opens over the top of Chrome, obscuring it.
So closing the browser is not immediately required but is recommended.
In the new versions of chrome, after installation in android it associate all the links in the "scope" to the PWA application, if you try to open a link in your chrome browser it open directly in the application.
hope that will answer your question
I'm using vidyo.io as videoconference solution in our platform. I'm having an issue with Vidyo's Chrome extension for screen sharing that is easily reproducible using the very own Vidyo's samples:
If you download Vidyo's web sample from developer portal, open samples/VidyoConnector/js/VidyoConnector.html in Chrome, choose 'Join via the browser', and click the 'Window share' select list (there is no need to start a conference to reproduce the error), Chrome will open the Vidyo Screen Share extension page twice, even if you already have the plugin installed. For this to work you have to uninstall the extension and reinstall it again. It will work until the end of the current session.
In the other hand if you go to Vidyo.io developer portal, choose "Demo" from "Developers" menu and start a conference using the "Join via the browser" button, click the same 'Window share' select list the Vidyo Screen Share extension works as expected, allowing you to pick a window or a screen to share.
In our implementation we're having the same problem as the code from web sample listed above, but if an example of our code would be of any help to clarify the issue, here you have an excerpt (we're using Angular, and here you have some TypeScript code):
private vidyoConnector: VidyoClientLib.VidyoClient.VidyoConnector;
(...)
selectedWindowShare(share: VidyoClientLib.VidyoClient.VidyoLocalWindowShare) {
this.vidyoConnector.SelectLocalWindowShare({localWindowShare: share})
}
This issue happens only on Chrome. When we use Firefox it works seamlessly. I'm using Chrome 69 on OSX High Sierra.
Any suggestion on how to solve this will be much appreciated. Thanks in advance!
If I am not mistaken, you are either running the VidyoConnector.html directly in the browser or hosting the sample on non-secured hosting (HTTP).
For the Vidyo Screen Share Chrome extension to work correctly, you need to host it on a secured hosting (HTTPS).
You can verify this by using our hosted sample here:
https://static.vidyo.io/latest/connector/VidyoConnector.html
Hope this helps.
On both of my Macs I'm having an odd font display problem for the Dashboard which loads the spring.io website. I've tried multiple versions of STS and two different Macs running Sierra. If I look at other sites via the dashboard, generally it displays fine and if I use an external browser like Safari or Chrome the site displays correctly. It is only in the Dashboard that this problem exists. Further, this problem does not exist if I go to preferences/dashboard and select use old dashboard. The styling goes back to the old method but the font problem is not there at least.
Switch to old dashboard from preference menu.
I see in many videos how the web applications are run on server in Exclipse and are previewed inside the IDE, without opening the actual browser. Is that possible in Netbeans?
Yes, that is possible. From the menu go to Tools->Options. In the General tab you see the Web Browser setting. Select the Embedded WebKit Browser.
We are developing an Eclipse plugin that opens web pages in a view using the Eclipse web browser (typically IE on Windows).
Are there any testing tools that support Eclipse (to drive the parts using Eclipse/RCP) and also able to drive the web browser views.
At a minimum I'd want to be able to get elements by ID or xpath, and to send click events to elements in the browser.
We know Quick Test Pro doesnt do this, and can't see anything that explicitly supports Eclipse web browser views.
You can check with QFS , we used this tool for SWT/JFace UI automation and this tool also supports web. You can to check if this supports your test case.