On Wed, Jul 26, 2017 at 11:07 AM, <gsquel...@mozilla.com> wrote: > I think that such an API could be spec'd such that it is portable, with > the output being flexible enough that we can put Mozilla-specific > information in there. E.g.: A fixed API to get the data, and a minimal > structure for the output, but say, each log message could have a free-form > 'data' json object, or some self-described tabular data. >
The latter approach has generally turned out to be a mistake. Often, all it achieves is to shift compatibility problems to a different level, where the problems may not be recognized, or there may be no standards process to deal with them, or the usual methods for feature detection do not work. If you want to have Mozilla-specific extensions, be honest about it and just add them to the WebExtensions API. One option here might be to have an API that returns strings of human-readable text, although that's dangerous too because people might try to parse it. Rob -- lbir ye,ea yer.tnietoehr rdn rdsme,anea lurpr edna e hnysnenh hhe uresyf toD selthor stor edna siewaoeodm or v sstvr esBa kbvted,t rdsme,aoreseoouoto o l euetiuruewFa kbn e hnystoivateweh uresyf tulsa rehr rdm or rnea lurpr .a war hsrer holsa rodvted,t nenh hneireseoouot.tniesiewaoeivatewt sstvr esn _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
