Strangely empty looking BCD table

That page was composed from a project that pulls in all old Kuma content and using some reverse engineering tries to make .json files similar to how build-json works.

The JSON for this page is as follows:

      {
        "type": "browser_compatibility",
        "value": {
          "resolve": {
            "__compat": {
              "mdn_url": "https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/API/dns/resolve",
              "support": {
                "chrome": {
                  "version_added": false
                },
                "edge": {
                  "version_added": false
                },
                "firefox": {
                  "version_added": "60"
                },
                "firefox_android": {
                  "version_added": "60"
                },
                "opera": {
                  "version_added": false
                }
              }
            }
          }
        }
      }

https://gist.github.com/peterbe/91d6a71a7d0f2b794dcdccfcc0caac64

It seems like there’s should at least be 1 extra row.

[peterbe]

Too old now.

[peterbe]

I should give some important context.

I’m working on a prototype where we take all the structured stuff that stumptown-content/scripts/build-json/build-json.js produces and puts into packaged AND this other script that I’m working on. What that script does is that it scrapes ALL content from Kuma. It finds the HTML for each page and looks at the use of {{Compat(ARGS)}} and then manually calls…

const { packageBCD } = require("../build-json/resolve-bcd");

...

        const bcdData = packageBCD(compat);
        return {
            type: "browser_compatibility",
            value: bcdData
        };

So there’s definitely an opportunity to do something with that bcdData struct. However, it would be nice to not have to but then we’re dragging in fixes for legacy into the stumptown-renderer’s BCD ingredient component (that you wrote @joedarc )

Perhaps @Elchi3 can weigh in?