Crash direct wrapping media element when media isn't enabled

Call createV8HTMLFallbackWrapper instead of createV8HTMLWrapper when dispatching a disabled MediaElement wrap. If media is disabled, createV8HTMLWrapper makes a crash when media element is created.  
    
Test: fast/media/media-disable-crash.html

BUG=N/A

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=159000

[gyuyoung-inactive, 2013-09-28 03:54:27]

Direct wrapping media makes a crash when media is disabled.

Below is a crash callstack.

STDERR: [18470:18470:0903/141811:62960482128:ERROR:renderer_main.cc(227)]
Running without renderer sandbox
STDERR: ASSERTION FAILED: actualInfo->derefObjectFunction ==
info.derefObjectFunction
STDERR: gen/blink/bindings/V8HTMLElement.cpp(773) : static
v8::Handle<v8::Object>
WebCore::V8HTMLElement::createWrapper(WTF::PassRefPtr<WebCore::HTMLElement>,
v8::Handle<v8::Object>, v8::Isolate*)

[gyuyoung-inactive, 2013-10-05 14:24:45]

Add tkent to reviewer. I think we need to return a fallback wrapper instead of
direct wrapper when media is disabled.

Though the direct wrapper was added by WebKit Bug 103431, I don't understand why
we should return a direct wrapper.

https://bugs.webkit.org/show_bug.cgi?id=103431

I think a fallback wrapper is proper in this case. Test case came from WebKit
Bug 119951.

[tkent, 2013-10-06 22:38:00]

+dcarney, haraken

[haraken, 2013-10-06 23:57:08]

LGTM. I agree that creating a fallback wrapper is a right thing to do here.

[commit-bot: I haz the power, 2013-10-06 23:58:43]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/gyuyoung.kim@samsung.com/23684014/9001

[commit-bot: I haz the power, 2013-10-07 02:02:36]

Change committed as 159000