Skip to content
This repository was archived by the owner on Jun 21, 2022. It is now read-only.

Fix aggregation of privacy features#322

Merged
wbamberg merged 2 commits intomdn:masterfrom
Elchi3:webext-privacy
Sep 22, 2017
Merged

Fix aggregation of privacy features#322
wbamberg merged 2 commits intomdn:masterfrom
Elchi3:webext-privacy

Conversation

@Elchi3
Copy link
Member

@Elchi3 Elchi3 commented Sep 20, 2017

@Elchi3 Elchi3 requested a review from wbamberg September 20, 2017 10:27
@wbamberg
Copy link

Thanks for fixing this. I noticed it yesterday but didn't have time to look into it.

It seems that the underlying problem is that we're generating tables with depth 1, but these parts of the tree don't have any compat data at depth 1. So an alternative way to fix it is to remove the special-casing for devtools and privacy, and instead generate tables with a depth of 2 (or 10, or...)[1].

The side-effect of that is that we then list compat data for subfeatures like Tab.incognito, but maybe that's not a bad thing?

@Elchi3, what do you think?

[1] on that topic, I wish there was a simple way to say "iterate through all the subfeatures, as deep as you have to". I thought maybe we could have it do if you omit the depth argument, it means that? So depth means, "limit depth to"?

@Elchi3
Copy link
Member Author

Elchi3 commented Sep 21, 2017

It seems that the underlying problem is that we're generating tables with depth 1, but these parts of the tree don't have any compat data at depth 1. So an alternative way to fix it is to remove the special-casing for devtools and privacy, and instead generate tables with a depth of 2 (or 10, or...)[1].

Yes, I thought about just removing special-casing here and just use a depth of 2. But as that adds a lot other things to the tables on the page I was unsure about it and only wanted to provide a quick fix here.
On a second look, just using a depth level of 2 works just fine I think. I can change this to do that. Let me know.

[1] on that topic, I wish there was a simple way to say "iterate through all the subfeatures, as deep as you have to". I thought maybe we could have it do if you omit the depth argument, it means that? So depth means, "limit depth to"?

Yes, likely something we should do. Somewhat out of scope for this hotfix I would say, though.

@wbamberg
Copy link

On a second look, just using a depth level of 2 works just fine I think. I can change this to do that. Let me know.

Yes, I think this would be better :).

Copy link

@wbamberg wbamberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @Elchi3 !

@wbamberg wbamberg merged commit 0244f90 into mdn:master Sep 22, 2017
jwhitlock added a commit to mdn/kuma that referenced this pull request Sep 25, 2017
* mdn/kumascript#321 - Compat: Use footnotes for alternate name
* mdn/kumascript#322 - WebExtAllCompatTables: aggregation of privacy features
* mdn/kumascript#326 - Compat: Update for BCD v0.0.7
@Elchi3 Elchi3 deleted the webext-privacy branch October 31, 2017 10:02
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants