56bf7dbdaf
In current implementation we don't support nested scheduled break at all. If one break was scheduled inside another and second one doesn't produce actual break (execution was in blackboxed code or no JavaScript was executed) then second one will clear first scheduled break even if any not blackboxed JavaScript will be executed later.
Ambiguous break reason is added for the case when we have more then one scheduled reason. "auxData" in this case contains object with array of { reason: reason, auxData: auxData } objects for each reason in 'reasons' property.
BUG=chromium:632405
Review-Url: https://codereview.chromium.org/2678313002
Cr-Commit-Position: refs/heads/master@{#43021}
42 lines
930 B
Plaintext
42 lines
930 B
Plaintext
Checks nested scheduled break in framework code.
|
|
break reason: framework-break
|
|
break aux data: {
|
|
"data": "data for framework-break"
|
|
}
|
|
doFrameworkBreak (framework.js:20:2)
|
|
doFrameworkWork (framework.js:15:2)
|
|
frameworkCall (framework.js:9:2)
|
|
testFunction (user.js:27:2)
|
|
(anonymous) (expr.js:0:0)
|
|
|
|
break reason: ambiguous
|
|
break aux data: {
|
|
"reasons": [
|
|
{
|
|
"reason": "top-scheduled-break"
|
|
},
|
|
{
|
|
"reason": "top-framework-scheduled-break",
|
|
"auxData": {
|
|
"data": "data for top-framework-scheduled-break"
|
|
}
|
|
}
|
|
]
|
|
}
|
|
callback (user.js:31:17)
|
|
doFrameworkWork (framework.js:16:2)
|
|
frameworkCall (framework.js:9:2)
|
|
testFunction (user.js:27:2)
|
|
(anonymous) (expr.js:0:0)
|
|
|
|
break reason: user-break
|
|
break aux data: {
|
|
"data": "data for user-break"
|
|
}
|
|
callback (user.js:32:2)
|
|
doFrameworkWork (framework.js:16:2)
|
|
frameworkCall (framework.js:9:2)
|
|
testFunction (user.js:27:2)
|
|
(anonymous) (expr.js:0:0)
|
|
|