Looks like the way I handled getting the context doesn't account for query strings, which, among other possible problems, means that the parameters object is not accurate in the inspector.
I'm not sure if the Chrome Tabs API will give information about the query string or not. It seems odd that it wouldn't, but I don't immediately see anything regarding query strings in the Chrome Tabs API documentation.
Looks like the way I handled getting the context doesn't account for query strings, which, among other possible problems, means that the
parametersobject is not accurate in the inspector.I'm not sure if the Chrome Tabs API will give information about the query string or not. It seems odd that it wouldn't, but I don't immediately see anything regarding query strings in the Chrome Tabs API documentation.