4 ms·
Funny, I've been using the MDN docs and took a look at the Chrome docs today. Some of the conceptual info was easier to track on the Chrome docs where the Mozil
by joshka 4y ago
Funny, I've been using the MDN docs and took a look at the Chrome docs today. Some of the conceptual info was easier to track on the Chrome docs where the Mozilla side seemed to jump too low level too quickly.
Ideally, those docs should just be in one place so writing Chrome/Safari/Firefox extensions should just work.
- eyelidlessness 4y ago> the Mozilla side seemed to jump too low level too quickly This is literally my only complaint about MDN, and it’s only a complaint when I’m in a hurry. The sprawling body of standards MDN documents are almost all fairly low level and intended as such, and MDN mostly does a good job of balancing the low level details with good boilerplate examples. I can’t say how this is for extensions on any version, but if the MDN docs continue apace I’d be surprised if they don’t at least adequately answer this “should” as shortly behind a stable spec as anyone could wish for. I wish XML-related tech was such a hot documentation commodity… guess I better contribute as I go :)
- ctxc 4y agoHey! What things related to xml are you working on? I for one went through the signing and stuff and it was pretty rough going.
- eyelidlessness 4y agoI maintain the Enketo[1] projects for ODK[2]. The latter is a little more flexible and stable on the XML front, but the former is currently in the position of using a lot of nonstandard XML tooling despite being well positioned to use existing browser tech, and at the same time may be better off migrating to many of the same abstractions ODK already uses. 1: https://github.com/enketo https://github.com/enketo 2: https://github.com/getodk https://github.com/getodk