Using css :not() inside hx-trigger target: selector with parentheses is a syntax error.

[teak]

Using a css :not() selector inside of an hx-trigger="click target:( ... )" should be valid. The following example causes a generic htmx:syntax:error with no explanation:

hx-trigger="click target:(td:not(.no-click) *)"

Using {} has the same error. My guess is incorrect parentheses parsing.

[MichaelWest22]

Yeah sorry their are some limits to the parsing support for sub css selectors in triggers. Spaces are hard to support here but there is support for wrapping in parentheses but it does not allow you to combine that with inner parentheses like this as it treats it as a single css selector (td:not(.no-click) with an extra unexpected syntax of *) at the end.

target:td:not(.no-click)>*
target:td.clickable>*
target:(td.clickable *)

Here are a few options that may work for you as direct children >* does not use whitespace or you can use a positive clickable selector instead of a negative not() causing your issues.