@svcx80 That would depend on a number of factors, but there are several possible outcomes: WebKit and the spec both change to match Chrome's behavior; Chrome changes to match the spec's behavior; the spec changes in a way that invalidates both/all implementations, etc. etc.