Jan de Mooij 4c8da76923 Bug 1816311 - Don't expose objects through findPath with --fuzzing-safe. r=jonco ... The issue in the bug is that we were returning a `DebugEnvironmentProxy` to JS through `findPath`/`UbiNode`, and this object isn't safe to use from arbitrary JS. This patch also changes `findPath` to not define the `node` property with `--fuzzing-safe`, to fix similar issues elsewhere. This `DebugEnvironmentProxy` case is easy to fix, but the engine also uses plain objects and arrays internally in some places and the `JSClass` checks won't be sufficient for that. Differential Revision: https://phabricator.services.mozilla.com/D169912		2023-02-17 14:58:35 +00:00
..
examples
loader	Bug 1815180 : Dump error message when import maps aren't allowed. r=jonco	2023-02-08 12:22:04 +00:00
public	Bug 1814105: part 1 - Record offsets directly instead of through a Label, and add string support for recording instructions r=iain	2023-02-16 14:07:55 +00:00
src	Bug 1816311 - Don't expose objects through findPath with --fuzzing-safe. r=jonco	2023-02-17 14:58:35 +00:00
xpconnect	Backed out changeset 3cdcc72baa6e (bug 1776755) for causing failures at test_ext_contentscript_triggeringPrincipal.js.	2023-02-14 19:30:16 +02:00
app.mozbuild
ffi.configure
moz.build
moz.configure	Bug 1809206 - wasm: Add wasm-no-experimental config and try job. r=tcampbell	2023-02-17 00:11:38 +00:00
sub.configure