Chore: cleanup data in notes

[queengooborg]

As I was reviewing the Samsung Internet mirroring PRs, I noticed various points of data expressed in the notes that had significant information regarding the support in the browser. For example, in Chrome Android, there was support from the initial release, but then there was a note indicating how it's only supported in Windows and Linux. Obviously, this should make Chrome Android support false instead.

When we have some time, we should skim through the notes and update their data, removing redundant information and overall cleaning up.

(Speaking of, do we want to keep our "This value is recognized, but has no effect." notes?
We had a discussion about this somewhere, but I can't remember what the outcome was.)

[ddbeck]

(Speaking of, do we want to keep our "This value is recognized, but has no effect." notes?
We had a discussion about this somewhere, but I can't remember what the outcome was.)

I think this was the end of that discussion: #3904 (comment). The short answer is yes, keep the notes. The discussion was more about how it interacted with "partial_implementation": if you have a real version number for such a (mis-)feature, set "partial_implementation": true and keep the note. If you don't have a real version number, keep the note and set "version_added": false. In other words, it's an editorial decision that privileges version number accuracy over the correctness of the "partial_implementation" flag.

I ought to write this up in the data policies doc.

[ddbeck]

I ought to write this up in the data policies doc.

Oh wait I already did, though I didn't address the notes question specifically.

[Elchi3]

I'm closing this stalled issue. I think the introduction of "mirror" cleaned out a lot of weird notes.