ChromeClientEfl always are created with view and it will not be removed until destroyed.
So, we don't need to check whether m_view is null.
Created attachment 97895 [details]
Comment on attachment 97895 [details]
Should not you have ASSERTs instead then?
Created attachment 97898 [details]
(In reply to comment #2)
> (From update of attachment 97895 [details])
> Should not you have ASSERTs instead then?
Thanks for your comment.
m_view is only changed When called constructor of ChromeClientEfl.
Does we need to add ASSERT before calling m_view every time?
Almost other methods of ChromeClientEfl use m_view without checking m_view.
The commit-queue encountered the following flaky tests while processing attachment 97898 [details]:
http/tests/local/formdata/send-form-data.html bug 63034 (author: firstname.lastname@example.org)
The commit-queue is continuing to process your patch.
Comment on attachment 97898 [details]
Clearing flags on attachment: 97898
Committed r89327: <http://trac.webkit.org/changeset/89327>
All reviewed patches have been landed. Closing bug.