Details
-
Bug
-
Resolution: Duplicate
-
P2: Important
-
None
-
4.6.0
-
None
Description
After the switch to the JavaScriptCore-based QtScript back-end, there were some behavioral differences compared to 4.5. These should be resolved.
For each issue, either the new behavior should be accepted, or the 4.5 behavior should be restored.
Attachments
Issue Links
- depends on
-
QTBUG-11012 [Reg] Crash / incorrect result when setting custom scope chain for a native context
-
- Closed
-
-
QTBUG-17612 [Reg] Dynamic C++ property overrides JS property
-
- Closed
-
-
QTBUG-18188 [Reg] Contexts created with QScriptEngine::pushContext() are not clean
-
- Closed
-
-
QTBUG-6132 QScriptContext::isCalledAsConstructor() returns the wrong result for JS contexts when JIT is enabled
-
- Closed
-
-
QTBUG-6133 QScriptContextInfo::functionMetaIndex() doesn't return the correct index for overloaded slots
-
- Closed
-
-
QTBUG-6135 [Reg] 'debugger' statement returns undefined regardless of QScriptEngineAgent's return value
-
- Closed
-
-
QTBUG-6136 QRegExp <--> RegExp conversion is not fully bidirectional
-
- Closed
-
-
QTBUG-6138 [Reg] Error objects lack lineNumber and fileName properties when they're not thrown
-
- Closed
-
-
QTBUG-6139 QScriptEngine::uncaughtExceptionBacktrace() doesn't give a full backtrace
-
- Closed
-