How to deal with `ref` attributes? about block-interactivity-experiments

[DAreRodz]

@SantosGuillamot, I've been taking a look at this issue, and I think we can ignore the ref attribute while generating virtual nodes, i.e., something like:

diff --git a/src/runtime/vdom.js b/src/runtime/vdom.js
index 5657128..b11cec9 100644
--- a/src/runtime/vdom.js
+++ b/src/runtime/vdom.js
@@ -24,6 +24,8 @@ export default function toVdom(node) {
 			const [, prefix, suffix] = /wp-([^:]+):?(.*)$/.exec(n);
 			wpDirectives[prefix] = wpDirectives[prefix] || {};
 			wpDirectives[prefix][suffix || 'default'] = val;
+		} else if (n === 'ref') {
+			continue;
 		} else {
 			props[n] = attributes[i].value;
 		}

What does this imply? Practically nothing, because even if the ref attribute is not saved in the props generated by running toVdom(), the attribute remains in the DOM node after hydrating; it is not removed.

There could be problems if that node is in any part of the DOM that is unmounted and mounted again, in which case there would be two possibilities:

1. The third-party library that handles the ref attribute has already been run before hydrate, so the changes it makes are most likely already in the DOM, and everything will work as usual.
2. This third-party library runs after hydration; if that happens, when unmounting and re-mounting the node, it is most likely that this third-party library will not be executed again, so it doesn't matter if ref is there or not. 🤷