I imagine if I’m implementing leedohm’s idea, that I can. But if I’m doing that, then I’m hacking around the provided mechanisms of using CSS selectors. Like, either the selectors work, or they don’t. And if they don’t, then they should be removed because it’s additional code and cognitive overhead which I have to realize must be circumvented.
Also, this is how I’m attempting to do it right now:
which isn’t working, but I can’t figure out why, since every time I press escape, the keybinding resolver gets closed! Guess I could try unsetting all of those and then like binary search it to figure out which one is overriding, it’s just that I think my selector should has higher specificity (I’m assuming the matching selector is based on where the cursor is, which I think is what defines the active element, but it would be really convenient if I could see what DOM path is being matched against). Probably this is all stuff I can implement myself if I learn more about how the editor works, but it would still make it more accessible to dabblers like me if reflective tools like this were available.