Android Intent not opeining in Android Chrome recent version 110 - javascript

I am trying to open to UPI payment link in the chrome browser on mobile devices but it's failing, I cannot figure out the exact reason.
failures observed in
chrome:110, android 12, nokia device
passed in
chrome:110, android 11, one plus device,
safari: 16, ios 16,
firefox
sample UPI links
<a target="_self" href="upi://pay?pa=Naukri.payu#indus&pn=Info Edge India Limited&tr=16796361409&am=1.00">Link1</a>
<a target="_self" href="upi://pay? pa=jeevansathi1.payu#hdfcbank&pn=Info Edge India Limited&tr=16796449075&am=1.00">Link2</a>
<a target="_self" href="upi://pay?tr=202101345671229366&tid=121313202101345671229366&pa=juspay#axisbank&mc=1234&pn= Merchant%20Inc&am=1.00&cu=INR&tn=Pay%20for%20merchant">Link3</a>

Related

How to force a link to open in safari instead of webview?

IOS webviews do not support WebRTC - only Safari on IOS does.
How can I force a page/link to open in real Safari, instead of a webview?
For example, the Gmail app opens all links inside a webview. Instead, I want them to open in Safari.

JW Player not playing in some browsers

I'm experiencing a very strange behavior of the embedded JW Player. Generally, it plays videos fine in
Safari 10.0.2 (Mac)
Internet Explorer 11 (Windows)
Edge 25.1 (Windows)
Mobile Safari (iOS 10.2)
It also plays fine in all other browsers, but only when I open the video on the preview page in the JW Player Backend (see screenshot, tested in Chrome 55 for Mac).
However, it doesn't play when I embed the player in my Project (locally or in productivity, even if I use the same markup used in the preview page), but only in some browsers, including
Chrome 55.0 (Mac)
Opera 42.0 (Mac)
Firefox 50.1 (Mac)
Chrome 55.0 (Windows)
Firefox 50.0 (Windows)
In these Browsers, the player shows the loading icon for about 1 minute, then it says "Error loading media: File could not be played" (see screenshot, tested in Chrome 55 for Mac).
However, the browsers listed at the beginning can still play the video...
And it doesn't seem to be only me, since my colleagues are experiencing the exact same problem. Can anybody help?
Here's an example embed (expires in 1 day):
<script type='text/javascript' src='http://content.jwplatform.com/players/rUqzk7Ff-JGyYovz4.js?exp=1484212670&sig=e492a1f9aab8910829dabae0e97a1d5a'></script>

Unable to inspect iOS devices in Safari 8.0.8

I connected my iPad device running iOS 9 beta version to Mac Running Yosemite 10.10.5 and not getting option to inspect in Safari 8.0.8 under Develop menu.
Things i did
In device settings->safari->Enabled Web inspector and JavaScript.
In Safari preferences on Mac machine enabled "Show Develop menu in
menu bar".
Any help is appreciated.
Thanks
Not sure about iOS9, but for previous versions you needed to use new beta version of desktop Safari to debug beta version of mobile Safari. Probably this is the same problem.

What are valid deviceNames for Chrome emulation testing with Protractor?

The common web consensus seems to be that if you see a name in your chrome emulator, you can use it as-is in your protractor config ... so I tried Apple iPad:
{
browserName: 'chrome',
chromeOptions: {
mobileEmulation: {
deviceName: 'Apple iPad'
}
}
}
But I had to muck around until trial & error yielded the correct deviceName to be: Apple iPad 3 / 4
Now I've searched here: https://developer.chrome.com/devtools/docs/device-mode#enable-device-mode and here: https://sites.google.com/a/chromium.org/chromedriver/mobile-emulation
but I can't find a list of all the valid deviceNames. Any ideas where to get it?
On https://code.google.com/p/chromium/codesearch I found: https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit/Source/devtools/front_end/emulated_devices/module.json&q=%22Apple%20iPad%22&sq=package:chromium&type=cs&l=643
But that's not really the source code that matters.
Maybe the source code for chrome webdriver somewhere else may have an enumerated list but I couldn't find it, any help is appreciated!
So I found some sources but they seemed to referencing links that didn't exist anymore. This seems to be the best result I could find?
https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit/Source/devtools/front_end/emulation/OverridesUI.js&l=338
EDIT:
This list seems like the master list
https://code.google.com/p/chromium/codesearch#chromium/src/chrome/test/chromedriver/chrome/mobile_device_list.cc
This code contains supported devices:
https://cs.chromium.org/chromium/src/chrome/test/chromedriver/chrome/mobile_device_list.cc?type=cs&q=%22Apple+iPhone+6%22&sq=package:chromium&l=12
For the moment it contains:
Laptop with touch
BlackBerry Z30
Google Nexus 6
Google Nexus 7
Google Nexus 4
Google Nexus 5
Apple iPad
Laptop with HiDPI screen
Samsung Galaxy Note II
Nokia N9
Samsung Galaxy S4
Nokia Lumia 520
BlackBerry PlayBook
Apple iPhone 5
Apple iPhone 4
Apple iPhone 6
LG Optimus L70
Apple iPhone 6 Plus
Apple iPad Mini
Amazon Kindle Fire HDX
Samsung Galaxy S III
Laptop with MDPI screen
Samsung Galaxy Note 3
Google Nexus 10

window.open on Windows Phone 7

I am looking for any information, or help with an issue I am having with Mobile IE9 on Windows Phone 7 Mango; although I would settle for a resolution on Windows Phone 7 in general.
<input type="button" value="input" onclick="window.open('http://www.google.com')" />
<span onclick="window.open('http://www.google.com')">span</span>
anchor
I am using this.
http://jsfiddle.net/ag7wU/1/embedded/result/
When I select any of these elements on the Windows Phone 7.0/7.1, I navigate to google.com. On every other browser I can readily find, a new window/tab is created: Chrome, Firefox 6.0, Opera 11.50, IE9, Safari, WebKit on BB OSv6, Dolphin on Android 2.3.3, Dolphin on android 3.2, and mobile safari on the IPhone and IPad.
The only exception is windows phone 7. The best solution I can find is to use the anchor tag and href attribute, and instruct users that they are going to have to hold down the links they want, and select "open in new tab" Am I missing something?
You should always provide a fallback for environments that do not support multiple tabs and windows (or JavaScript).
You want to make sure that the browser can display a real URL when the user hovers over the link, and that the link is long-press/right-click copyable.
You also want to preserve link URLs for indexers, link checkers, offline archivers like archive.org, and other robots.
anchor

Categories