Re:Web Components Aren't Framework Components
by lelanthran on Tuesday December 12, 2023 @12:41AM
(#38609935)
That breaks on edge cases.
For example it won't work recursively when a fetched fragment has fragments of its own.
Or when the js snippet loads before some fragment element is loaded (say, from a DOM update).
The nice thing about custom elements is that you get to treat them exactly like normal elements.
Re:Web Components Aren't Framework Components
by mewpmewp2 on Tuesday December 12, 2023 @05:56PM
(#38619950)
In this case you could use MutationObserver - although we are doing manually the logic web components provide, but my point is that you can do it also without using web components. My code doesn't include attribute changes, but this should be possible to also do with MutationObserver.
<body>
<script>
const onRemoteFragmentMount = async (el) => {
const src = el.getAttribute("src");
const result = await fetch(src).then((res) => res.text());
el.innerHTML = result;
};
const callback = (mutationsList, observer) => {
for (let mutation of mutationsList) {
if (mutation.type === "childList") {
mutation.addedNodes.forEach((node) => {
if (node.tagName === "REMOTE-FRAGMENT") {
onRemoteFragmentMount(node);
}
});
}
}
};
const observer = new MutationObserver(callback);
const bodyElement = document.querySelector("body");
observer.observe(bodyElement, {
childList: true,
subtree: true,
});
</script>
<remote-fragment src="..." />
</body>
Re:Web Components Aren't Framework Components
by KatrinaKitten on Tuesday December 12, 2023 @06:00PM
(#38620000)
While you certainly could do this, a major benefit of web components is that you get all of this for free out of the box. It's less error/mistake prone, keeps your code cleaner and more obvious exactly what it does, etc.
You could querySelectorAll and check the src attribute etc, then fetch the content put it in the innerHTML.
Or if you want to react to any such component inserted at times down the line or src attribute changes, you could use MutationObserver.