Not sure what the right area is for the MDN doc stuff.

Added Area-HTML, Triaged labels.

Set owner to amouravski@google.com.

Added this to the M3 milestone.

Removed Area-HTML label.
Added Area-DartDoc label.

This comment was originally written by amouravski@google.com

Appears to be fixed?
http://api.dartlang.org/docs/releases/latest/dart_indexed_db/Database.html#transaction

Added NeedsInfo label.

Well, they are all gone. :)

Removed this from the M3 milestone.
Added this to the M4 milestone.

This comment was originally written by amouravski@google.com

Well, it's definitely the case that MDN docs are out of date.

The only reason that the IndexedDB stuff was working before is because it was actually going down an incorrect path that happened to give semi-decent results.

Specifically, the MDN docs were being reused for IndexedDB from other classes. So, that's why sethladd first saw docs that were somewhat off.

The MDN docs need to be regenerated, and I'm going to take a look at it today, but the code is out of date (and doesn't work as written currently.)
The last time it was updated at all was Aug. 29, 2012: dart-archive/bleeding_edge-DEPRECATED-USE-SDK-INSTEAD@74d2d8a
The last time I can basically confirm it worked was over a year ago on Feb. 7, 2012: dart-archive/bleeding_edge-DEPRECATED-USE-SDK-INSTEAD@ff35a64#dart/utils/apidoc/mdn

The steps that need to happen:

0. Determine how important keeping MDN docs updated is. The following steps might take a considerable amount of work, compared to writing good docs ourselves. That's a lot of work, too, but might be better over time.

1. Update the dartIdl.json and domTypes.json. I can't even figure out how these were generated, so, this is probably something that could be bundled with the scripts in tools/dom/scripts . Presumably, when the IDL changes, it should update dartIdl.json. Same with domTypes.json.

2. Update the scripts under utils/apidoc/mdn to ensure they work. If we're going to keep these scripts around for awhile having some rudimentary tests on them would be helpful.

Further, we're running sh, js, and dart scripts in a row, and I think they're fairly brittle. If we had a simple set of scripts in a single language, I think that'd be better. We could remove the node dependency, at least, and I don't know many people on the team who know how to debug node stuff. I'm not saying we should rewrite all of the scripts, but at one point or another, I think it'll be necessary.

3. Re-run everything every so often to keep docs fresh.

Please advise.

cc @jacob314.
cc @blois.
Removed the owner.
Added PatchesWelcome label.

This comment was originally written by @sethladd

If we do want to maintain the script, we should consider also pulling docs from webplatform.org. More and more docs will show up there.

This comment was originally written by amouravski@google.com

sethladd: I asked webplatform.org people about that, and they said that it's nowhere near a state where people should be pulling docs from them and it probably won't be for a year or more.

Removed this from the M4 milestone.
Added this to the M5 milestone.

Removed this from the M5 milestone.
Added this to the Later milestone.
Removed Type-Defect label.
Added Type-Enhancement label.
Changed the title to: "Set up a mechanism to keep the MDN docs current".

Added old-dartdoc label.

Issue #16573 has been merged into this issue.

Issue #16621 has been merged into this issue.

Added Pkg-DartDoc label.

Removed Area-DartDoc label.
Added Area-Pkg label.

Removed Pkg-DartDoc label.
Added Pkg-DocGen label.

Issue #17977 has been merged into this issue.