Confirmed users
796
edits
Compatibility/Telemetry: Difference between revisions
→Measuring web compatibility: Reorg a bit. Clean up some of the description around video.
(→Q1 probe goals: FRext profiles will be captured with the rest.) |
(→Measuring web compatibility: Reorg a bit. Clean up some of the description around video.) |
||
| Line 9: | Line 9: | ||
These are the probes we want to try to land in Q1. Please only add to this list if you're willing to take on the required work. | These are the probes we want to try to land in Q1. Please only add to this list if you're willing to take on the required work. | ||
===== WAP (WML or XHTMLMP) content type ===== | |||
We not infrequently receive bugs in Bugzilla about WAP content being sent to Fennec and Firefox OS users (see [https://bugzilla.mozilla.org/show_bug.cgi?id=941241 bug 941241], [https://bugzilla.mozilla.org/show_bug.cgi?id=997668 bug 997668], with dependencies, among others.). We intend to gather telemetry data to understand how common this is for Firefox mobile users. Once we understand the frequency and severity of the problem (measured as WAP vs non-WAP content type responses) we can decide how to proceed. Possible decisions include: support re-parsing of WAP content as HTML, showing an error message in the developer console, WONTFIXing related bugs and continuing to do Tech Evangelism as issues arise. | We not infrequently receive bugs in Bugzilla about WAP content being sent to Fennec and Firefox OS users (see [https://bugzilla.mozilla.org/show_bug.cgi?id=941241 bug 941241], [https://bugzilla.mozilla.org/show_bug.cgi?id=997668 bug 997668], with dependencies, among others.). We intend to gather telemetry data to understand how common this is for Firefox mobile users. Once we understand the frequency and severity of the problem (measured as WAP vs non-WAP content type responses) we can decide how to proceed. Possible decisions include: support re-parsing of WAP content as HTML, showing an error message in the developer console, WONTFIXing related bugs and continuing to do Tech Evangelism as issues arise. | ||
A telemetry probe (HTTP_WAP_CONTENT_TYPE_RECEIVED histogram) was landed in [https://bugzilla.mozilla.org/show_bug.cgi?id=1121559 bug 1121559] on January 21, 2015. | A telemetry probe (HTTP_WAP_CONTENT_TYPE_RECEIVED histogram) was landed in [https://bugzilla.mozilla.org/show_bug.cgi?id=1121559 bug 1121559] on January 21, 2015. | ||
===== Video ===== | |||
* Media MIME types | |||
We need to gather telemetry on the videos being used in the wild. This directly tells us what features matter for openh264 development and for our own products. It also helps us track uptake use of other codecs such as h265 or proprietary dolby digital audio codecs, for example. | |||
* Media formats and MIME types | |||
** HTMLMediaElement.canPlayType() | ** HTMLMediaElement.canPlayType() | ||
** MediaSource.isTypeSupported() | ** MediaSource.isTypeSupported() | ||
** MediaSource.addSourceBuffer(DOMString type) | ** MediaSource.addSourceBuffer(DOMString type) | ||
** ogg, mp4, h264, m3u8/HLS, etc. | |||
* H264 | * H264 | ||
** | ** h264 profile and level, measured from canPlayType() (See [https://bugzilla.mozilla.org/show_bug.cgi?id=1125340 Bug 1125340]) | ||
** h264 profile and level, measured from decoded SPS (see [https://bugzilla.mozilla.org/show_bug.cgi?id=1125340 Bug 1125340]) | |||
** SPS.max_num_ref_frames (see [https://bugzilla.mozilla.org/show_bug.cgi?id=1131706 Bug 1131706]) | ** SPS.max_num_ref_frames (see [https://bugzilla.mozilla.org/show_bug.cgi?id=1131706 Bug 1131706]) | ||