Re-implement didCreateScriptContext to RenderFrameObserverEfl.
authorDongJun Kim <djmix.kim@samsung.com>
Wed, 2 Dec 2015 00:43:44 +0000 (09:43 +0900)
committerYoungsoo Choi <kenshin.choi@samsung.com>
Tue, 10 Jul 2018 07:55:23 +0000 (07:55 +0000)
commit4cc8eebe15e697514c2896c52846bc6415b789e1
tree91b8fb60879ff8a86c32c3247582c15f78e10b04
parent3abc52d704e1f307af5adc42a5f1dbae9a3fd0c1
Re-implement didCreateScriptContext to RenderFrameObserverEfl.

DidCreateScriptContext and WillReleaseScriptContext are moved
to ContentRendererClient by (1),(2) in opensource.

DidCreateScriptContext and WillReleaseScriptContext are called
when calling open/close window by javascript.
Those functions must be called together.

In case of m47 chromium-efl, we do not call DidCreateScriptContext.
For this reason, renderer process is crashed when
javascript context is released from injected_bundle.

This patch has 2 modifications as below.
- Remove |WillReleaseScriptContext| from ContentRendererClientEfl.
- Move |didCreateScriptContext| to RenderFrameObserverEfl.

(1) https://codereview.chromium.org/1040403003
(2) https://codereview.chromium.org/185713008

Bug: http://107.108.218.239/bugzilla/show_bug.cgi?id=15036

Reviewed by: a.renevier, a1.gomes, djmix.kim, g.czajkowski, msu.koo

Change-Id: I008937710d08472a6cfb77a51b1cbf01ffacc221
Signed-off-by: DongJun Kim <djmix.kim@samsung.com>
tizen_src/ewk/efl_integration/renderer/content_renderer_client_efl.cc
tizen_src/ewk/efl_integration/renderer/content_renderer_client_efl.h
tizen_src/ewk/efl_integration/renderer/render_frame_observer_efl.cc
tizen_src/ewk/efl_integration/renderer/render_frame_observer_efl.h