diff options
| author | haraken@chromium.org <haraken@chromium.org@bbb929c8-8fbe-4397-9dbb-9b2b20218538> | 2014-05-22 01:02:54 +0000 |
|---|---|---|
| committer | haraken@chromium.org <haraken@chromium.org@bbb929c8-8fbe-4397-9dbb-9b2b20218538> | 2014-05-22 01:02:54 +0000 |
| commit | cd86d76c09d7763bbbde35a3e5252149bf78e261 (patch) | |
| tree | 71871eeb8ad5e704db7a02066b3637d5bd5dce0f /third_party/WebKit/LayoutTests/fast/canvas/canvas-putImageData.js | |
| parent | b5d1bc8f8d9df1017aaef8bd12745401a9225d0e (diff) | |
| download | chromium_src-cd86d76c09d7763bbbde35a3e5252149bf78e261.zip chromium_src-cd86d76c09d7763bbbde35a3e5252149bf78e261.tar.gz chromium_src-cd86d76c09d7763bbbde35a3e5252149bf78e261.tar.bz2 | |
Remove GetCurrentContext from V8Window::toV8
The code removed in this CL is now just for performance optimization (Previously it might have been not, but now it is just for performance optimization). Now that I refactored toV8Context(), we can always get a correct context by calling toV8Context(). Thus the removed code is not needed for correctness.
Another interesting fact is that the removed code is not contributing to performance optimization at all. This is because:
- In a case where we can get the context from the GetCurrentContext(), it means that the context is already initialized.
- Then we can simply call toV8Context() to get the context, because it is guaranteed that the toV8Context() doesn't hit the heavy operation of context initialization.
In conclusion, the removed code is now no help. Thus this CL removes it.
BUG=357144
Review URL: https://codereview.chromium.org/293003007
git-svn-id: svn://svn.chromium.org/blink/trunk@174499 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Diffstat (limited to 'third_party/WebKit/LayoutTests/fast/canvas/canvas-putImageData.js')
0 files changed, 0 insertions, 0 deletions