The idl-test-harness can't detect the multiple types in webidl [1], so it doesn't know about the type like "double or AutoKeyword".
The same problem also happen in VTTCue's line property, and we have already expected its fail.
Therefore, we should expect this fail before we fix the problem of idl-test-harness.
[1] http://searchfox.org/mozilla-central/source/dom/imptests/idlharness.js#375
MozReview-Commit-ID: 5XvOwdmqKDP
--HG--
extra : rebase_source : fd72ef43d1f24792a1b3e228da7a7dca9483b1da
To determine if an issue has been solved, go through the possible prefs that
would have been saved by the front-end, to see if any previously-unplayable
formats/key systems are now playable, in which case we notify the frontend, to
record the issue-solved telemetry.
MozReview-Commit-ID: DmU50i6FtG8
Combine notification type and web-console string id into structs, simpler to
pass around, and will be useful to go through them when checking for solved
issues.
MozReview-Commit-ID: Hy3bMG3m12V
Renamed AppendToStringList to AppendToFormatsList, to distinguish from other
string-based lists.
Ensure that list items don't contain commas, as commas are used as separators,
and we don't want&need to introduce escaping.
Added FormatsListContains.
MozReview-Commit-ID: 8KpuhSjCW3d
Utility class&function that creates an iteratable range from a comma-separated
string, where each iteration will give a dependent substring (i.e., no string
copy happening).
This will help with going through lists of unplayable formats, to see if
issues have been solved.
If useful enough, this could later be published to a more public location
(e.g. mfbt or xpcom).
MozReview-Commit-ID: 3XP5PwQZFA1
When an issue is reported, save the unplayable formats/key-systesm in a pref,
keyed by the detailed issue string id, and report the infobar-shown telemetry.
More telemetry when the "Show me how" button is clicked.
And final telemetry (and clearing the prefs) when the issue is solved.
MozReview-Commit-ID: 4PgaPMVfjsQ
Fill up extra details in notification: Web-console notification string id (will
be used as telemetry key), and whether the issue is present or has been solved.
MozReview-Commit-ID: AzhuIvGqb2p
This helps determine how each format is affected by some issues. It will be
needed in later patches, to see when the issue get fixed (by noticing that
these formats become playable again).
MozReview-Commit-ID: 2wFzmnX5rBY
Instead of having yet-another variable, just infer playability from the lists
of playable&unplayable formats, which we need to look at anyway.
MozReview-Commit-ID: ABc2WtWADzN
This can be used to test Decoder Doctor on Windows, but disabling WMF through
prefs, to trigger an Decoder Doctor infobar.
MozReview-Commit-ID: 1aRk111VFO7
Due to the conflation, we were returning the wrong thing on get_attribute,
Updated tests to call get_property when that is what they meant.
MozReview-Commit-ID: AY6bd3RECvV
--HG--
extra : rebase_source : d4063cb5f923ff48a408269bf9a4ee72198b707e
Using the Selenium atom we are conflating properties and attributes which is not
thing we really want to be doing.
MozReview-Commit-ID: HdZOz1jQrwz
--HG--
extra : rebase_source : 70118dba39bb1a72e78a264d2a71beff3671f9cb
