Test for Bug 31375 - Web Inspector: breakpoints in named evals are not restored after a reload

- open this page with Web Inspector

- switch to the Scripts panel, enabling debug if required

- the available scripts in the select element should be:

  - (program): f1.js
  - (program): f2.js
  - bp-in-named-eval-after-reload.html

- In `(program) f1.js`, set a breakpoint on the first executable line of the function `f1()`, the invocation of `doNothing()`.

- In `(program) f2.js`, set a breakpoint on the first executable line of the function `f2()`, the invocation of `doNothing()`.

- click this button:

- debugger should stop in the `f1()` function.

- resume the debugger

- debugger should stop in the `f2()` function (the function in `(program) f2.js`)

- resume the debugger

- switch to the web page, reload the web page, switch back to web inspector

- in the breakpoints sidebar panel, click on the two breakpoints listed and the source for those functions should be shown in the source panel, and the previous breakpoint markers should be visible

- click the "click me" button above, again

- debugger should stop in the `f1()` function.

- resume the debugger

- debugger should stop in the `f2()` function.

- resume the debugger

Note that without the fix in Bug 31375, the breakpoints won't work after reloading the page.