Allow phone access deselect itself

71 views
Skip to first unread message

James MnemoNeco

unread,
Feb 17, 2022, 5:33:51 AM2/17/22
to Tasker
Hi, im trying to use webview element with javascript ( opening navigation, making phone calls ) but option "allow phone access" is deselecting itself always when i leave element edit. Non of javascript is working. Phone is samsung fold 3

thanks for help

j.

mibu

unread,
Jul 4, 2022, 4:17:22 PM7/4/22
to Tasker
Hi, same issue on an Nvidia Shield TV. On my Oneplus 7t it works flawlessly. Any hint appreciated.

BR, Michael

SportyRydr

unread,
Jul 14, 2022, 7:22:07 PM7/14/22
to Tasker
I think I'm having a similar issue after the last or next to last Tasker update. In my case I can't tap on, scroll, or zoom webview elements. (Interestingly, it DOES scroll when I have my phone connected to my computer with scrcpy and use my mouse wheel.) I looked at a particular webview element's Allow Phone Access option, and it was ENABLED. So, I disabled it and went and tried the scene (thinking maybe if I toggle it off/on, it will "reset" the option); still didn't work. So I went back into the webview's properties to turn Phone Access back on, and it was already enabled. So, on my OnePlus 7 Pro, it automatically REselects itself. Hmmm.

V/r,
SR

SportyRydr

unread,
Jul 14, 2022, 7:37:51 PM7/14/22
to Tasker
Forgot to mention, I have one scene in which the webview element DOES scroll and tap—probably zoom too, but I don't have zooming enabled in that one. It's newer than the scenes whose webview elements don't scroll etc., but it's still like 2 years old. I'm trying to see if there are any differences in their properties. FWIW.

SportyRydr

unread,
Jul 14, 2022, 7:56:22 PM7/14/22
to Tasker
Ok, it looks like I've fixed my issue. Maybe this will fix someone else's too.

It was the elements' depths. I mean, they'd always worked previously, so I don't know if it's a bug, or an update changed the different elements' depth levels, or what. So, in the one that still worked, the webview was at depth 4, and the "scene border" element that I use on all the scenes in this project was at 3. But in one of the ones that stopped working, the webview was 4, but the scene border was 5; when I changed the scene border to 3, it restored the functionality. WOO HOO!

ktmom

unread,
Jul 15, 2022, 8:17:45 AM7/15/22
to Tasker
Yeah, most of my scenes were effected by the update.  Things like element widths and heights got changed so they obscured the ability to tap on other elements.  Took a while to figure out why my scenes no longer worked.
Reply all
Reply to author
Forward
0 new messages