yes ) it was always
as i'm not editing the core code of Logseq and working "on top of it", there are some limitations ((
no possibility to show Logseq "native placeholder", not good idea to hide it at all, cose you will have no clickable zone...

for now...

@yoyurec Sorry for I'm not sure if I understood. I understood the clickable zone part. Is it possible to separate it in to 2 cases? If it's not a pure property block (like my screenshots) then hide it, or it's a pure property block then show a line as a clickable zone?

Btw in this case, I'm trying to use the toc:: no property to stop some blocks show in the toc generator plugin and trying to hide it XD

Logseq has props blocks. They have a background color...
When you hide props via custom names Logseq config.edn OR using system predefined such as icon:: and there is no other visible items in the list - Logseq shows "Properties" text (as on my screen) and not 'backgrounded-props-block',
I can't do the same (at least for now).

Plugin hides props lines via CSS/JS, not Logseq system! So Logseq continues to think that there is/are prop(s) and shows it as styled block (((

not looking to who (Logseq/plugin) and how (placeholder text "Properties" / props block) doing this - you NEED to have something to click on to edit!

so i will not hide 'all-items-hidden-but-still-visible-props-colored-block' due UX

even if i mimic Logseq behavior - you will see same "noise" in your content - something like this

so a possible solution for you - hide blocks via custom.css, killing UX in honor of UI )))

@yoyurec Thank you for the explanation now I understood, wish Logseq would have a better solution for this XDXD