Allow Amethyst to send application names to custom layouts

[ianyh]

Discussed in #1425

^{Originally posted by ianyh February 17, 2023}
As it stands now we explicitly do not pass application information along with window frames when asking custom layout for appropriate frames. A user was requesting something for custom layouts in which they could apply special layout rules to some lower priority applications that should not affect the tiling. With the app information restriction this is effectively impossible, but I wanted to ask for feedback on how acceptable it would be to include application names along with window frames sent to custom layouts.

A brief explanation for why that information is not included is that Amethyst has privileged access to information through Accessibility, and custom layouts are basically arbitrary JavaScript so I wanted to minimize how much privileged information was passed along. Any application can determine what other applications are running, but they cannot necessarily tie those applications to window frames.

There is information that I don't want to ever pass along, but the open question right now is whether or not tying window frames to application names is acceptable. What do people think?

[jasonprado]

I would like this feature. I was surprised the information wasn't passed along when I looked at custom layouts, but the security issue you raise makes sense.

Can you make the JavaScript execute in a very sandboxed way? No modules, no fetch, no filesystem access.