From a7948a7519c3b0d4660637e8697311bd8abdc85d Mon Sep 17 00:00:00 2001 From: Lars Knoll Date: Mon, 15 Oct 2018 14:43:17 +0200 Subject: Properly mark variables as unresolved when accessed from eval If we can't resolve the variable and are executing eval code, we need to look it up by name, and not generate a lookup in the global object. Change-Id: I693b3b714651911f72620160bfc463d6dbb00820 Reviewed-by: Simon Hausmann --- tests/auto/qml/ecmascripttests/TestExpectations | 1 - 1 file changed, 1 deletion(-) (limited to 'tests/auto/qml/ecmascripttests') diff --git a/tests/auto/qml/ecmascripttests/TestExpectations b/tests/auto/qml/ecmascripttests/TestExpectations index 81f9318cdc..02cb6acf99 100644 --- a/tests/auto/qml/ecmascripttests/TestExpectations +++ b/tests/auto/qml/ecmascripttests/TestExpectations @@ -567,7 +567,6 @@ language/expressions/prefix-increment/S11.4.4_A5_T3.js sloppyFails language/expressions/prefix-increment/S11.4.4_A5_T4.js sloppyFails language/expressions/prefix-increment/S11.4.4_A5_T5.js fails language/expressions/prefix-increment/S11.4.4_A6_T3.js fails -language/expressions/tagged-template/cache-eval-inner-function.js strictFails language/expressions/tagged-template/invalid-escape-sequences.js fails language/expressions/tagged-template/tco-member.js strictFails language/function-code/each-param-has-own-non-shared-eval-scope.js sloppyFails -- cgit v1.2.3