Make placeholder block optional

[julianrubisch]

Feature Request

Describe the solution you'd like

sometimes you don't want a placeholder at all for a given element, so ideally a block would not be required as a placeholder.

[julianrubisch]

I'm starting to wonder if that's maybe a special case for eager: true

I think it could be sufficient to make the placeholder optional when eager is true

[rickychilcott]

My intended use case is for rendering actions or buttons that are dependant on a users permission levels. hacked together example is at https://sleepy-sea-13861.herokuapp.com/?showAll=true

In my case, I really don't want a spinner or anything to indicate that it's loading, but the button can pop in when it's returned from the server. I think you're right that I may make it eager: true, but I guess I'm failing to see why it's required at all.

[julianrubisch]

Why what is required? The placeholder?

Because something needs to trigger the intersectionobserver. But eager: true short circuits that anyway, so maybe we can make the placeholder optional if eager is true?

[rickychilcott]

Yeah, I think I understand the technical reasons why a placeholder is needed, but what I don't understand is why it needs to be user-provided.

Can the placeholder default to something like tag.div or tag.span if a placeholder is not provided? I know we need an element on the page to trigger intersectionobserver, but does an empty element work?

[julianrubisch]

Ah I see! Well yes and no, it can be a default but it needs to be actually visible.

[julianrubisch]

Maybe we could make everything a bit simpler and say, if no placeholder, make it an eager element.

Could deprecate eager in the future...