Preview URLs

• https://pr13664.content.dev.mdn.mozit.cloud/en-US/docs/Web/API/MIDIInput/midimessage_event
• https://pr13664.content.dev.mdn.mozit.cloud/en-US/docs/Web/API/MIDIInput
• https://pr13664.content.dev.mdn.mozit.cloud/en-US/docs/Web/API/MIDIMessageEvent/data
• https://pr13664.content.dev.mdn.mozit.cloud/en-US/docs/Web/API/MIDIMessageEvent
• https://pr13664.content.dev.mdn.mozit.cloud/en-US/docs/Web/API/Web_MIDI_API

Flaws

Note! 3 documents with no flaws that don't need to be listed. 🎉

URL: /en-US/docs/Web/API/MIDIInput
Title: MIDIInput
on GitHub
Flaw count: 1

• bad_bcd_links:
  • no explanation!

URL: /en-US/docs/Web/API/MIDIInput/midimessage_event
Title: MIDIInput: midimessage event
on GitHub
Flaw count: 1

• broken_links:
  • Can't resolve /en-US/Web/API/Web_MIDI_API

External URLs

URL: /en-US/docs/Web/API/MIDIInput
Title: MIDIInput
on GitHub

No new external URLs

URL: /en-US/docs/Web/API/MIDIInput/midimessage_event
Title: MIDIInput: midimessage event
on GitHub

• https://www.midi.org/specifications-old/item/table-1-summary-of-midi-message (1 time) (Note! This may be a new URL 👀)

URL: /en-US/docs/Web/API/Web_MIDI_API
Title: Web MIDI API
on GitHub

No new external URLs

URL: /en-US/docs/Web/API/MIDIMessageEvent
Title: MIDIMessageEvent
on GitHub

No new external URLs

URL: /en-US/docs/Web/API/MIDIMessageEvent/data
Title: MIDIMessageEvent.data
on GitHub

No new external URLs

(this comment was updated 2022-03-10 13:53:07.917779)

Checklist I used for reviewing this event Content PR:

When onXYZ exists, for each onXYZ

• Redirect from /Web/API/xxxx/onXYZ to /Web/API/xxxx/XYZ_event` set
• /Web/API/xxxx/onXYZ deleted.
• In /Web/API/xxxx/XYZ_event:
  • Front-runner YAML: Correct browser-compat front-runner key
  • Front-runner YAML: Correct title front-runner key to: Interface: XYZ event (with ticks!)
  • Front-runner YAML: No Property and Event Handler int the tag list but Event in it (more cleaning possible)
  • Check if the event bubbles. If not, no mention in article
  • Intro explain the event itself and no more just onXYZ.

    Example: "The levelchange event of the Battery Status API is fired when the battery {{domxref("BatteryManager.level","level")}} property is updated."

  • No HTML table with Bubbles, Cancelable, and Interface lines.
  • Syntax section with the structure of the template, and fix the names of event and of the onXYZ property
  • If inheritance is not only Event, there is an Event type section (two texts possible!, with
    • {{InheritanceDiagram}} with the right argument
    • There is an Event properties section and list the parameters, taken from the interface of the event type
  • Check that no mention of this onXYZ is a link.
  • Check that links to other onXYZ are links to the corresponding XYZ_event

On the API interface page:

• There is no Event handlers section
• There is an Events section (with the correct events)
• Check that there are no links to onXYZ.

On each page of the interface and the API overview page:

• Check that there are no links to onXYZ.
• Check that examples uses the modern syntax for defining function in event handler (onXYZ = event => { …} )
• Check that no {{event} macro is left.
• Fix flaws (as much as possible); at least, make sure not to introduce new flaws.
• Check that if an event is linked to a property value, that property documents when this event is fired.

  Example: "When its value changes, the chargingchange event is fired."

Optional:

• Remove gremlins (non-breaking spaces, curly tick, curly double-ticks)
• If the interface is no more experimental, remove the experimental tags/banners.

Administration:

• Link to the BCD PR.

I think I've address everything @teoli2003 I just need to take a look at bcd next 👍