By default, the W3C process actually requires multiple implementations before something is supposed to be standardised. So it is actually necessary that browser

By default, the W3C process actually requires multiple implementations before something is supposed to be standardised. So it is actually necessary that browser vendors ship vendor-specific implementations before the standards process can properly consider things like this. If Mozilla jumps on board and makes a compatible implementation that back ends to eg: local llama then you would have the preconditions necessary for it to become standardised. As long as Google hasn't booby trapped it by making it somehow highly specific to chrome / google / Gemini etc.