Re:Seeking an Answer: Why can't HTML alone do includes?
by j45 on Sunday May 04, 2025 @11:27AM
(#43887259)
It’s not ideal, but t it does exist in pure html… and the OP didn’t seem to note it.
A bit of vanilla JavaScript with WebComponents is a few lines:
Re:Seeking an Answer: Why can't HTML alone do includes?
by masklinn on Sunday May 04, 2025 @11:34AM
(#43887297)
> it does exist in pure html [...] JavaScript with WebComponents
You seem to have a rather original definition of "pure HTML".
Re:Seeking an Answer: Why can't HTML alone do includes?
by j45 on Sunday May 04, 2025 @12:41PM
(#43887742)
Typo, from the numerous fat finger typos you see above. :)
An html only option that exists is using object. Replying to the miss of the OP in case others might find it suitable.
If a tiny bit of vanilla JavaScript can be tolerated, WebComponents appear to have a broad standardized approach that is not framework dependant.
It was really shit. Browser navigation cues disappear, minor errors will fuck up the entire thing by navigating fixed element frames instead of contents, design flexibility disappears (even as consistent styling requires more efforts), frames don’t content-size so will clip and show scroll bars all over, debugging is absolute ass, …
And it increases resource use.