Zephyr Lykos

Results 252 comments of Zephyr Lykos

Should also match webpack ESM modules in `SequenceExpression`. Sample:

[unpacked_samples.tar.gz](https://github.com/j4k0xb/webcrack/files/13753961/sample.tar.gz) Some unpacked samples for further inspection. Notice how some webpack runtime globals still got persisted (search for regex `/require\./`)

It's possible to implement a bridge listening to libinput events in a privileged context (e.g. using pkexec) and send it to the main process in the user session.

I guess we can update the `_NET_FRAME_EXTENTS` Atom when updating the border values. Will look into it later

I'm afraid this isn't enough for picom to round the corner for windows with `i3-title`. picom currently round all edges of a window, which leads to this: ![image](https://user-images.githubusercontent.com/21154023/204016085-b3ef0462-777b-4bdd-b99b-f922d2a9409c.png) (Also you...

Hmm. About the shadow issue, although picom have `clip-shadow-above`, it's not able to handle the case when two frames interferes. Specifying border radius isn't possible now, but that should be...

tried the `i3-rounded` patch and seems it does not play nicely with borders and frames too.

just checked mpv and the title frame is acting weird too: ![image](https://user-images.githubusercontent.com/21154023/204021761-0b740ff4-a73f-4fd8-a384-d48b9f7ee83d.png)

![image](https://user-images.githubusercontent.com/21154023/204023507-1e1b8b82-4773-469c-be70-05688e43d57a.png) It also doesn't work well with tabbed/stacked mode as mention earlier, the i3-frame is a independent window in the tree.

I think the weird structure also caused this, but I'm not sure: