# Task: Get innerWidth & innerHeight of front window with elapsed time. Just for corroboration you might run this AppleScript in the Apple Script Editor.app with Safari already running:. This looks like another case of Bad Apple! How many extensions do you have loaded?.How much memory do you have on that machine?.I get pretty much what I'd expect with Safari 12.1.2 on macOS 10.12.6: JavaScript in Safari Time: 0.26 sec You must enable before it can be triggered. JavaScript in Safari This Macro was uploaded in a DISABLED state. (Macro was written & tested using KM 9.0+ on macOS 10.14.5 (Mojave)) DOWNLOAD Macro File: I ran the same test in Chrome, and it was very fast: Just a guess since I don't have a Mac like that to test. Maybe Safari behaves differently with the new Macs with M1. So I am running a fairly recent (2019) iMac, but with macOS Mojave, and I am seeing the same behavior. I can confirm this behavior, an excessive amount of time to execute JavaScript in Safari, I also tested the Macro on my MacBook Air M1 and it ran as expected, so it seems to have something to do with my old work machine. Therefore I don't expect any solutions from you anymore, except maybe some hints for trouble shooting or experiences like "when I had something like this, resetting the PRAM worked" … What I realised when looking around in Safari, is that activating and deactivating extensions takes a very long time, too (spinning beachball included) The macro is working, but it's still taking the above mentioned unusual amount of time.The macro does not have any triggers, because it's launched from a palette. I went through the interactive help guide, which led me back here at the end.This seems to have fixed some typed string triggers that did not fire before (like your Macro to get the macOS version -). I could not unset the accessibility rights at first so I completely removed the apps from this pane and waited for KM to request the rights after another reboot. I have unset and reset the accessibility rights in System Prefs > Security & Privacy > Accessibility as well as in … > Input Monitoring.I have rebooted (Mac was off for the night).I have quit KM several times, Engine and/or Editor.%Variable%safari_viewport_width% × %Variable%safari_viewport_height% Save trimmed results without errors to variable “safari_viewport_height”.
0 Comments
Leave a Reply. |