mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
Gecko engine for Wine
0f21dd7253
From 49f5e33d79df3713bc510e611a5064858bf24e4a Mon Sep 17 00:00:00 2001 These files have specially crafted headers which should be rejected by the new checks added to resolve this bug. If any audio output is produced then this bug has re-occured. The audio data is the phrase "invalid file", in one or six channels, to make this more obvious. The new mochitest test_invalid_reject.html tries to load and play each of the new invalid files and verifies that an error event is triggered. Since the invalid data is in the file headers, this should happen after network load but before metadata is ready, so the test also asserts errors if loadedmetadata or a number of subsequent events are triggered. The test will time out if no error event is fired at all. Thanks to Matthew Gregan for assistance writing the mochitest. --- content/media/test/Makefile.in | 11 ++++++ content/media/test/invalid-cmap-s0c0.opus | Bin 0 -> 6835 bytes content/media/test/invalid-cmap-s0c2.opus | Bin 0 -> 6834 bytes content/media/test/invalid-cmap-s1c2.opus | Bin 0 -> 6848 bytes content/media/test/invalid-cmap-short.opus | Bin 0 -> 6854 bytes content/media/test/invalid-m0c0.opus | Bin 0 -> 2471 bytes content/media/test/invalid-m0c3.opus | Bin 0 -> 2471 bytes content/media/test/invalid-m1c0.opus | Bin 0 -> 6836 bytes content/media/test/invalid-m1c9.opus | Bin 0 -> 6836 bytes content/media/test/invalid-m2c0.opus | Bin 0 -> 2471 bytes content/media/test/invalid-m2c1.opus | Bin 0 -> 2455 bytes content/media/test/manifest.js | 14 ++++++++ content/media/test/test_invalid_reject.html | 52 ++++++++++++++++++++++++++++ 13 files changed, 77 insertions(+) create mode 100644 content/media/test/invalid-cmap-s0c0.opus create mode 100644 content/media/test/invalid-cmap-s0c2.opus create mode 100644 content/media/test/invalid-cmap-s1c2.opus create mode 100644 content/media/test/invalid-cmap-short.opus create mode 100644 content/media/test/invalid-m0c0.opus create mode 100644 content/media/test/invalid-m0c3.opus create mode 100644 content/media/test/invalid-m1c0.opus create mode 100644 content/media/test/invalid-m1c9.opus create mode 100644 content/media/test/invalid-m2c0.opus create mode 100644 content/media/test/invalid-m2c1.opus create mode 100644 content/media/test/test_invalid_reject.html |
||
|---|---|---|
| accessible | ||
| b2g | ||
| browser | ||
| build | ||
| caps | ||
| chrome | ||
| config | ||
| content | ||
| db/sqlite3 | ||
| dbm | ||
| docshell | ||
| dom | ||
| editor | ||
| embedding | ||
| extensions | ||
| gfx | ||
| hal | ||
| image | ||
| intl | ||
| ipc | ||
| js | ||
| layout | ||
| media | ||
| memory | ||
| mfbt | ||
| mobile | ||
| modules | ||
| mozglue | ||
| netwerk | ||
| nsprpub | ||
| other-licenses | ||
| parser | ||
| probes | ||
| profile | ||
| python | ||
| rdf | ||
| security | ||
| services | ||
| startupcache | ||
| storage | ||
| testing | ||
| toolkit | ||
| tools | ||
| uriloader | ||
| view | ||
| webapprt | ||
| widget | ||
| xpcom | ||
| xpfe | ||
| xulrunner | ||
| .gdbinit | ||
| .gitignore | ||
| .hgignore | ||
| .hgtags | ||
| aclocal.m4 | ||
| allmakefiles.sh | ||
| Android.mk | ||
| AUTHORS | ||
| client.mk | ||
| client.py | ||
| configure.in | ||
| LEGAL | ||
| LICENSE | ||
| mach | ||
| Makefile.in | ||
| mozilla-config.h.in | ||
| README.txt | ||
An explanation of the Mozilla Source Code Directory Structure and links to
project pages with documentation can be found at:
https://developer.mozilla.org/en/Mozilla_Source_Code_Directory_Structure
For information on how to build Mozilla from the source code, see:
http://developer.mozilla.org/en/docs/Build_Documentation
To have your bug fix / feature added to Mozilla, you should create a patch and
submit it to Bugzilla (https://bugzilla.mozilla.org). Instructions are at:
http://developer.mozilla.org/en/docs/Creating_a_patch
http://developer.mozilla.org/en/docs/Getting_your_patch_in_the_tree
If you have a question about developing Mozilla, and can't find the solution
on http://developer.mozilla.org, you can try asking your question in a
mozilla.* Usenet group, or on IRC at irc.mozilla.org. [The Mozilla news groups
are accessible on Google Groups, or news.mozilla.org with a NNTP reader.]
You can download nightly development builds from the Mozilla FTP server.
Keep in mind that nightly builds, which are used by Mozilla developers for
testing, may be buggy. Firefox nightlies, for example, can be found at:
ftp://ftp.mozilla.org/pub/firefox/nightly/latest-trunk/
- or -
http://nightly.mozilla.org/