sideshowbarker
sideshowbarker
Agreed this would be useful — and in general any statement in the spec that uses the word *should* is actually a normative statement. So any *should* statement in the...
Thanks @chrisdavidmills — is there a maintained endpoint I can POST some JSON to as part of the demo (and get a useful response back from)?
> Would http://www.jsontest.com/ be any use? Yes — thanks much, will use that
USE with polyfilll: - WebVTT - track element USE ... SOON(ISH) ... HOPEFULLY - defer attribute for scripts (no Opera) - async attribute for scripts (no Opera) - Typed Array...
>> @sideshowbarker @dontcallmedom Any idea how we could extract this info from the spec? I could try an awk script if nothing obvious appears. > > webref never uses data...
Just haven’t been able to make the time to keep it up to date. Please consider submitting patches to add anything you’ve noticed that’s missing but should be there. The...
For better or worse, XSLT works in all browser engines and as far as I know, no browser projects have any plans to remove it. In fact, we have a...
@caugner Thanks much — I just now pushed an update that switches this patch to instead calling `mdn.deprecated()` with a message parameter.
> Compat.test.js and Specifications.test.js need to be updated to pass `browser-compat` OK, thanks — I just now pushed an update which changes them to do that > and/or `spec-urls` via...
> @sideshowbarker Okay, now we only need to migrate our kitchensink page, moving the bcd key into the frontmatter: > > [mdn/content@`5fa776c`/files/en-us/mdn/kitchensink/index.md?plain=1#L241](https://github.com/mdn/content/blob/5fa776ca3c79d0298cdf07c50ed0024d8b185716/files/en-us/mdn/kitchensink/index.md?plain=1#L241) ah, ok, yes — just now opened https://github.com/mdn/content/pull/20480...