385
edits
| Line 49: | Line 49: | ||
* Explain the significant file formats, names, syntax, and semantics. | * Explain the significant file formats, names, syntax, and semantics. | ||
** AMCD describes to the browser how to connect/disconnect/get status and how to respond on success/failure, e.g., load a url | ** AMCD describes to the browser how to connect/disconnect/get status and how to respond on success/failure, e.g., load a url | ||
** AMCD is a JSON file | ** AMCD is a JSON file described in the spec | ||
** Status headers are comma and semicolon separated values describing each account and parsed with a custom parser | ** HTTP X-Account-Management-Status: Status headers are comma and semicolon separated values describing each account and parsed with a custom parser | ||
** Link headers are defined with [[https://datatracker.ietf.org/doc/draft-nottingham-http-link-header/ Web Linking standard]] and parsed with a custom parser | ** HTTP Link: <uri>; rel="acct-mgmt": Link headers are defined with [[https://datatracker.ietf.org/doc/draft-nottingham-http-link-header/ Web Linking standard]] and parsed with a custom parser | ||
* Are the externally visible interfaces documented clearly enough for a non-Mozilla developer to use them successfully? | * Are the externally visible interfaces documented clearly enough for a non-Mozilla developer to use them successfully? | ||
** For website-facing changes, documentation is in the spec and blog examples | |||
** For Firefox add-on facing api, not so much except existing code as a template | |||
* Does it change any existing interfaces? | * Does it change any existing interfaces? | ||
** No, but additional columns are added to the Password Manager database | |||
== Module interactions == | == Module interactions == | ||
edits