I have a ASP.NET site which offers JNLP files for starting Java Web Start applications. I've set them as hrefs in <a> tags to download them. The behaviour I get from different browsers varies:
IE11: Auto launch
Firefox (45): Auto launch
Chrome (48): Manual launch from the download bar
Edge: Manual launch from the download bar
Chrome is Chrome and I've pretty much given up hope on that, but can Edge be set to launch JNLP files instead of offering the "Open/Show downloads" bar?
Related
Opening up the developer menu (F12) in Edge instantly triggers Edge to start downloading all source map files. I mean all, all individual js files e.g. sap/m/Button-dbg.js.
It freezes up the browser and makes it impossible to do performance network tracing using the built in developer tools.
How can I stop this from doing that automatically?
Steps to reproduce:
Open MS Edge
Browse to https://sapui5.hana.ondemand.com/test-resources/sap/m/demokit/orderbrowser/webapp/test/mockServer.html
Once the webpage is completely loaded, press F12
You now notice it starts downloading all source map files for the UI5 framework (*-dbg.js)
Windows 10 1809 with Microsoft Edge 44.17763.831.0
source map files are downloaded unasked for
Windows 10 1909 with Microsoft Edge 44.18362.449.0:
no issues
In the app open STRG+ALT+SHIFT+S to open UI5 Dev. Tools, then -> Technical Settings -> Turn Debug-Sources off.
Every time I refresh the page Google Chrome Dev Tools switches to Sources tab which is getting very annoying. There is no breakpoint and there is no error so showing me random source files is pretty useless and damn irritating. It does not always do this for all web sites. If I have Console tab selected, how can I force it to stay on Console when refreshing? (67.0.3396.99 (Official Build) (64-bit))
I need to troubleshoot an issue happening in a webview running within my app. This issue only occurs on Android versions lower or equal to 4.3. My app requires an up to date version of Google Play services.
In order to troubleshoot my webview, I usually can run my app under the Android Emulator (with the latest version of Android), then connect to the web view via Chrome (using chrome://inspect) - the web view appears in Chrome and I'm able to browse the DOM and debug.
To run the app under 4.3, I've created (under AVD) a new device from an existing device definition,
then picked the target Google APIs (Google Inc.) - API Level 18. I've then installed my app, but when trying to run it, I get the error message "This app won't run unless you update Google Play services.". There's an "Update" button on the previous dialog, but nothing happen when clicking on it.
I then tried to debug my issue using Genymotion. I've created a device under 4.3, followed these instructions to flash my device with the latest Google Play services and installed my app. I can now run the app and reproduce the issue within this simulated environment.
The trick now is to be able to connect to the web view from my local Chrome browser. I've enabled remote debugging as described here. Now my device appears in Chrome, but the web view is not showing up in the inspector. Similarly, if I open a new tab under the native browser, it won't show up in the remote inspector. If I open a new tab under Android Chrome though, I can see it showing up under my remote Chrome inspector.
I can see two way moving forward and successfully accessing to the DOM of my webview:
Fixing the "Update" issue under the Android Emulator running 4.3
Or
Connecting to my web view from my Chrome inspector while running the app under Genymotion
Any idea on how to solve one of these two problems?
I have been using weinre for sometimes. it's a pretty good tool to debug webview for android 4.3 and lower. It provides almost same interface as chrome debugger.
All you need to do are:
Install weinre
sudo npm -g install weinre
Client side:
Insert the following code to your webpage <head> section.
Note: it's better to put it at end of <head> section, otherwise there will be some strange errors and debugger won't show up.
<script src="http://<your server ip here>:8081/target/target-script-min.js"></script>
Server side
weinre --boundHost -all- --httpPort 8081
Debugger
open the debugger tool from weinre from your desktop browser:
http://localhost:8081/client/
Finally,
select any target in Targets part and then start debugging.
Remote debugging web views only works on devices with android 4.4 and above.
have a look at this :
https://developer.chrome.com/devtools/docs/remote-debugging
I am new to Eclipse and I have created a small web app and it works but when I do Run on Server (Tomcat) from Eclipse it launches the website in its own internal web browser.
I wondered if it was possible to have it launch Firefox for example?
Do I need to download Aptana?
I would just enter the URL in your preferred browser, and bookmark it. As simple as that. You'll have to do it with different browsers anyway if you want to test the app on multiple browsers.
You can also choose which browser is used by going to Window - Preferences - General - Web Browser.
yes if u want your application to get started on firefox ..Go to window tab at the top of your eclipse IDE from there preferences and the go to general from there select browsers
check radio button of use external web browser and select the browser u want firefox or IE..
After installing my midlet to a phone over the air, I'm getting a blank page from browser which need to be closed manually.
Any idea how to prevent it?
I read that JAD files are no longer required, as the all info located in JAR. I tried to use the JAR files instead of JAD's, but with them the browser first downloads and only then offers to install the middlet. With JAD it offers to install first, which IMHO more user friendly. Is this the expected behavior, or it can be improved and remove the need in JAD's?
I'm using Eclipse MJT (Previously called EclipseME).
A JAD file makes it easier to sign and deploy your application.
I would definitely not expect all phones to be able to install an applicaiton from the JAR alone.
Without more information, I can see 2 reasons why a blank web browser page would be left on the screen after a jad install:
bug in handset firmware. Not only can the phone not download the jar without launching a full web browser but it also forgets to close the browser window. It happens.
your application asks the phone to notify a remote computer after installation. There is a standard application property for this in the MIDP specifications. it could be in the jad or in the manifest.