Is it possible to lock html elements for dom inspector?

[simonferndriger]

Is it possible to use AlpineJS mechanisms to make sure, that certain html elements cannot be changed and/or removed with the dom inspector?

[ekwoka]

You can use mutation observer to always force them to be readded/fixed...

But disabling JavaScript would also prevent that approach

So...what is the goal of this? Does it really matter?

[simonferndriger]

I undestand that this question is a bit off-topic. However, I was just thinking alound: if you implement a paywall, you want some content to be hidden (behind a blurry overlay for example). So, with the dom inspector, it's easy to remove that overlay. But it would be cool to just always reconstruct it after 😊

[ekwoka]

The way you handle a paywall is to not surface the whole article if the account isnt subscribed/logged in

Not to provide the whole article and then cover it up

[simonferndriger]

Yeah, I suspected that this is more a backend subject than frontend. Was just curious if there are now perhaps some new possibilties that would work wonders 😊

[ekwoka]

Nothing in the front end is secure

[simonferndriger]

It's just that I found out by coincidence, that when I change the value for @click= via dom inspector, it changed it back immediately after I made a change. That gave me the idea. It was probably due to a conditional template rendering though...

[SimoTod]

Even if you could do it, you can still read the full article in the dom inspector itself, bot can browse it, etc etc

[simonferndriger]

It's not an article in this case 😉 So there would be some additional steps anyway to get to the content (like loading additional scripts etc), so far, I was unable to hack it myself. But it would be nice to just keep the overlay anyway.