mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
Gecko engine for Wine
dbab286e15
While prior patches created new test directories
js/src/tests/ecma_5/strict and js/src/tests/js1_8_1/strict, they
failed to add jstests.list entries to their parent directories. This
adds them.
The strict tests generally were written to use assertEq, which is
simple and gives nice source positions in failure messages under the
JS shell. However, the jsreftests require each test file to call
reportCompare at least once. This adds a dummy call to reportCompare
to each file. It would be nice to make everything work in both
environments, perhaps using arguments.caller.
The test script js/src/tests/ecma_5/strict/13.1.js tried parsing
statements of the form 'function(x,x){}'. However, anonymous function
expressions are not allowed in a statement context when
JSOPTION_ANONFUNFIX is set. This is set under the browser, but clear
in the shell; bug 532233 suggests that the two be reconciled.
|
||
|---|---|---|
| accessible | ||
| browser | ||
| build | ||
| caps | ||
| chrome | ||
| config | ||
| content | ||
| db | ||
| dbm | ||
| docshell | ||
| dom | ||
| editor | ||
| embedding | ||
| extensions | ||
| gfx | ||
| intl | ||
| jpeg | ||
| js | ||
| layout | ||
| media | ||
| memory/jemalloc | ||
| modules | ||
| netwerk | ||
| nsprpub | ||
| other-licenses | ||
| parser | ||
| probes | ||
| profile | ||
| rdf | ||
| security | ||
| storage | ||
| testing | ||
| toolkit | ||
| tools | ||
| uriloader | ||
| view | ||
| webshell | ||
| widget | ||
| xpcom | ||
| xpfe | ||
| xpinstall | ||
| xulrunner | ||
| .hgignore | ||
| .hgtags | ||
| aclocal.m4 | ||
| allmakefiles.sh | ||
| client.mk | ||
| client.py | ||
| configure.in | ||
| LEGAL | ||
| LICENSE | ||
| Makefile.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 (http://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/