tangledhelix

cands, Yes as you found I did do an update to support the new React-based site. I didn't realize Packal wasn't maintained much. It would be nice if Alfred hosted some kind of registry itself, the way iOS has an App Store, or many languages have official repositories (npm for Node, pypi for Python, etc)...

Thanks, vitor! To answer your question, no, it did not work any differently in Script Editor. I assume I was simply running afoul of the browser's security model. Your suggestion to use tab.url worked out great, though. I am ready to push out a new version, it is all functional again.

I have an Alfred workflow based on a JXA script. It acts as a control mechanism for focusatwill.com (an online music streaming service). It has basic functionality, play/pause, skip track... This was working fine in an earlier version, interacting with the page using query selectors, e.g. tab.execute({ javascript: "document.querySelector('.playerControls .playButton').click();" }) This site recently refactored their UI to use React. My basic controls still work (using querySelector), but one part of the setup (changing the genre) has broken. It used to use querySelectorAll f

Updated to v1.3. This fixes a Javascript problem that crept up in Chrome at some point, and adds support for changing genre using an auto-complete list within Alfred.

Updated to v1.2, now supports "next track" function.

This workflow lets you play/pause a focusatwill.com tab in Google Chrome using a hotkey or a keyword. It won't activate Chrome, change the active tab, or otherwise disturb what you're otherwise working on. Download the workflow from Packal.