HTML Parser should produce 8 bit strings for doctype, comment and tagName tokens
https://bugs.webkit.org/show_bug.cgi?id=99889

Reviewed by Geoffrey Garen.

Added 8 bit check for accumulating all token data in MarkupTokenBase.  Added code to convert
"name" token data directly to a string (8 or 16 as appropriate).  Changed to accumulate
m_bufferedEndTagName as LChar's.

No new tests, covered by existing tests.

* html/parser/HTMLToken.h:
(HTMLToken):
* html/parser/HTMLTokenizer.cpp:
(WebCore::HTMLTokenizer::nextToken):
(WebCore::HTMLTokenizer::addToPossibleEndTag):
(WebCore::HTMLTokenizer::isAppropriateEndTag):
* html/parser/HTMLTokenizer.h:
(HTMLTokenizer):
* html/parser/HTMLTreeBuilder.cpp:
(WebCore::HTMLTreeBuilder::ExternalCharacterTokenBuffer::takeLeading):
* xml/parser/MarkupTokenBase.h:
(WebCore::MarkupTokenBase::beginStartTag):
(WebCore::MarkupTokenBase::beginEndTag):
(MarkupTokenBase):
(WebCore::MarkupTokenBase::beginDOCTYPE):
(WebCore::MarkupTokenBase::appendToComment):
(WebCore::MarkupTokenBase::appendToName):
(WebCore::MarkupTokenBase::nameString):
(WebCore::AtomicMarkupTokenBase::AtomicMarkupTokenBase):


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@132165 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[chromium] Move the call to RegisterIsolatedFileSystem to the WebTestDelegate interface
https://bugs.webkit.org/show_bug.cgi?id=100048

Reviewed by Adam Barth.

The call needs to be done outside of the sandbox.

* DumpRenderTree/chromium/TestRunner/public/WebTestDelegate.h:
(WebTestDelegate):
* DumpRenderTree/chromium/TestRunner/src/EventSender.cpp:
(WebTestRunner):
(WebTestRunner::EventSender::beginDragWithFiles):
* DumpRenderTree/chromium/TestRunner/src/TestDelegate.h:
(TestDelegate):
* DumpRenderTree/chromium/TestRunner/src/WebTestInterfaces.cpp:
(WebTestInterfaces::Internal):
(WebTestRunner::WebTestInterfaces::Internal::registerIsolatedFileSystem):
(WebTestRunner):
* DumpRenderTree/chromium/WebViewHost.cpp:
(WebViewHost::registerIsolatedFileSystem):
* DumpRenderTree/chromium/WebViewHost.h:
(WebViewHost):


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@132166 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Unreviewed, more Chromium ML expectation updating.

* platform/chromium-mac-mountainlion/TestExpectations:
* platform/chromium/TestExpectations:

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@132167 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Refactoring around ContainerNode::attachChildren
https://bugs.webkit.org/show_bug.cgi?id=99968

Reviewed by Hajime Morita.

Since ContainerNode::attach() is now equivalent to ContainerNode::attachChildren() + Node::attach(), we should call
ContainerNode::attach() instead of calling them.

No new tests, no change in behavior.

* dom/ContainerNode.h:
(ContainerNode):
* dom/Element.cpp:
(WebCore::Element::attach):
* dom/ShadowRoot.cpp:
(WebCore::ShadowRoot::attach):


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@132168 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Handle ArgumentCoder template specializations that take the ArgumentEncoder as a reference
https://bugs.webkit.org/show_bug.cgi?id=100056

Reviewed by Andreas Kling.

Use template magic to make it possible to have ArgumentCoder specializations where the encode
function takes the ArgumentEncoder object as a reference instead of as a pointer. Also, add an
operator<< to ArgumentEncoder and change the string related ArgumentCoder specializations over to taking
the encoder as a reference and using stream operators.

* Platform/CoreIPC/ArgumentCoders.cpp:
(CoreIPC::::encode):
* Platform/CoreIPC/ArgumentCoders.h:
* Platform/CoreIPC/ArgumentEncoder.h:
(ArgumentEncoder):
(UsesDeprecatedEncodeFunction):
(NoType):
(CoreIPC::ArgumentEncoder::encode):
(CoreIPC::ArgumentEncoder::operator<<):


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@132169 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Introduce Localizer::standAloneMonthLabels
https://bugs.webkit.org/show_bug.cgi?id=99963

Reviewed by Kentaro Hara.

Source/WebCore:

We realized full month names and full stand-alone month names were
necessary for input[type=month] UI. We change the compile-flag for
Localizer::monthLabels from "ENABLE(CALENDAR_PICKER)" to
"ENABLE(CALENDAR_PICKER) || ENABLE(INPUT_MULTIPLE_FIELDS_UI)," and
introduce Localizer::standAloneMonthLabels.

Tests: Add some test cases to Source/WebKit/chromium/LocaleMacTest.cpp
and LocalizedDateICUTest.cpp.

* platform/text/Localizer.h:
(Localizer):
- Add pure virtual standAloneMonthLabels.
- Change the condition for monthLabels.

* platform/text/LocaleNone.cpp:
(LocaleNone): Declare monthLabels, standAloneMonthLabels, and m_monthLabels.
(WebCore::LocaleNone::monthLabels):
Added. It always returns English month names.
(WebCore::LocaleNone::standAloneMonthLabels):
Added. Just calls monthLabels.

* platform/text/LocaleWin.h:
(LocaleWin):
Declare standAloneMonthLabels, and change the condition for monthLabels.
* platform/text/LocaleWin.cpp:
(WebCore): Change the condition for monthLabels.
(WebCore::LocaleWin::standAloneMonthLabels):
Added. Just calls monthLabels.

* platform/text/mac/LocaleMac.h:
(LocaleMac):
- Add standAloneMonthLabels and m_standAloneMonthLabels
- Change the condition for monthLabels and m_monthLabels.
* platform/text/mac/LocaleMac.mm:
(WebCore): Change the condition for monthLabels.
(WebCore::LocaleMac::standAloneMonthLabels):
Added. Get the information with NSDateFormatter::standaloneMonthSymbols.

* platform/text/LocaleICU.h:
(LocaleICU):
- Add standAloneMonthLabels and m_standAloneMonthLabels
- Change the condition for monthLabels and m_monthLabels.
* platform/text/LocaleICU.cpp:
(WebCore::LocaleICU::initializeCalendar):
Remove m_monthLabels initialization in order to avoid dependecy from monthLabels.
(WebCore):
(WebCore::createFallbackMonthLabels): Change the compile condition.
(WebCore::LocaleICU::monthLabels):
- Change the compile condition.
- Don't depend on initializeCalendar to make the code for
ENABLE(INPUT_MULTIPLE_FIELDS_UI) && !ENABLE(CALENDAR_PICKER) minimal.
(WebCore::LocaleICU::standAloneMonthLabels):
Added. The code is similar to shortStandAloneMonthLabels.

Source/WebKit/chromium:

Note that we don't add tests to LocaleWinTest because new function
LocaleWin::standAloneMonthLabels is equivalent to monthLabels.

* tests/LocaleMacTest.cpp:
(LocaleMacTest::standAloneMonthLabel): Added a helper function.
(TEST_F): Add some tests. We don't test ru_ru locale because it has
different data on OSX versions.
* tests/LocalizedDateICUTest.cpp:
(LocalizedDateICUTest::standAloneMonthLabel): Added a helper function.
(TEST_F): Add some tests.

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@132170 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[Chromium] Needs to track ShadowRoot usage
https://bugs.webkit.org/show_bug.cgi?id=99955

Reviewed by Dimitri Glazkov.

Added an UMA instrumentation.

* dom/ShadowRoot.cpp:
(WebCore::determineUsageType):
(WebCore):
(WebCore::ShadowRoot::create):


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@132171 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Label position is wrong in the suggestion picker when all the suggestions have labels
https://bugs.webkit.org/show_bug.cgi?id=99965

Reviewed by Kent Tamura.

Somehow the scrollbar was appearing and so the label element was being wrapped to the next line.

No new tests. Can't reproduce in layout test.

* Resources/pagepopups/suggestionPicker.css:
(.suggestion-list):
* Resources/pagepopups/suggestionPicker.js:
(SuggestionPicker.prototype._fixWindowSize): Explicitly show the scroll bar.


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@132172 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[chromium] Suppress compositor invalidations during FrameView recreation in force-compositing-mode
https://bugs.webkit.org/show_bug.cgi?id=99882

Patch by James Robinson <jamesr@chromium.org> on 2012-10-22
Reviewed by Adrienne Walker.

In force compositing mode, page navigation temporarily takes us in and out of compositing mode because the
root GraphicsLayer is owned by the FrameView which is destroyed and recreated. These changes generate
invalidations on the WebViewClient that trigger frames but aren't actually terribly useful. WebCore suppresses
repaints too early during page load to avoid flashing white or mostly white and to avoid impacting page load time.

This suppresses compositor invalidations during FrameView recreation.

Covered by chromium's page cycler performance tests.

* src/WebFrameImpl.cpp:
(WebKit::WebFrameImpl::commitDocumentData):
(WebKit::WebFrameImpl::createFrameView):
* src/WebViewImpl.cpp:
(WebKit::WebViewImpl::WebViewImpl):
(WebKit::WebViewImpl::suppressInvalidations):
(WebKit):
(WebKit::WebViewImpl::setRootGraphicsLayer):
(WebKit::WebViewImpl::scheduleComposite):
* src/WebViewImpl.h:
(WebViewImpl):

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@132173 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[Shadow] Fallback content should also be reprojection.
https://bugs.webkit.org/show_bug.cgi?id=99750

Reviewed by Dimitri Glazkov.

Source/WebCore:

Fallback content of InsertionPoint should be reprojected. The existing assumption that
only the direct child of host element can be distributed to InsertionPoint does not hold anymore.
So, if the parent of an element is InsertionPoint which should show fallback element, we have to
check the grand parent of the element instead of the element.

Tests: fast/dom/shadow/content-reprojection-fallback-reprojection.html
       fast/dom/shadow/content-reprojection-fallback.html

* css/StyleResolver.cpp:
(WebCore::shouldResetStyleInheritance): Checks the grandparent of the element if the parent is
an InsertionPoint which uses fallback content.
* dom/ComposedShadowTreeWalker.cpp:
(WebCore::shadowOfParentForDistribution):
(WebCore):
(WebCore::resolveReprojection):
(WebCore::ComposedShadowTreeWalker::traverseParent):
* html/shadow/InsertionPoint.cpp:
(WebCore::InsertionPoint::shouldUseFallbackElements): True if the InsertionPoint should use fallback content.
(WebCore):
* html/shadow/InsertionPoint.h:
(WebCore::parentElementForDistribution): Returns the grandparent element if the parent is InsertionPoint which uses
fallback content. Returns parent element otherwise.
(WebCore):

LayoutTests:

* fast/dom/shadow/content-reprojection-fallback-expected.html: Added.
* fast/dom/shadow/content-reprojection-fallback-reprojection-expected.html: Added.
* fast/dom/shadow/content-reprojection-fallback-reprojection.html: Added.
* fast/dom/shadow/content-reprojection-fallback.html: Added.


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@132174 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Include path in the repaint-text-decoration-style.html should be changed.
https://bugs.webkit.org/show_bug.cgi?id=100063

Unreviewed gardening.

The include path is differentiated by http://trac.webkit.org/changeset/132043

Patch by Dongwoo Joshua Im <dw.im@samsung.com> on 2012-10-22

* fast/css3-text/css3-text-decoration/repaint/repaint-text-decoration-style.html:

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@132175 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Assertion failed at WebCore::toInsertionPoint / WebCore::ContentDistributor::distribute
https://bugs.webkit.org/show_bug.cgi?id=100038

Reviewed by Kent Tamura.

Source/WebCore:

isHTMLContentElement() assumes that the content element always has
a tag name "content" but it doesn't when Shadow DOM feature is
disabled. This fix let the function see the correct tag name.

Test: fast/dom/shadow/insertion-points-with-shadow-disabled.html

* html/shadow/HTMLContentElement.cpp:
(WebCore::HTMLContentElement::contentTagName):
* html/shadow/HTMLContentElement.h:
(HTMLContentElement):
(WebCore::isHTMLContentElement):

LayoutTests:

* fast/dom/shadow/insertion-points-with-shadow-disabled-expected.txt: Added.
* fast/dom/shadow/insertion-points-with-shadow-disabled.html: Added.


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@132176 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[BlackBerry] Missing some cookies in HTTP response header when set several cookies in one "Set-Cookie" header.
https://bugs.webkit.org/show_bug.cgi?id=99950

Patch by Peter Wang <peter.wang@torchmobile.com.cn> on 2012-10-22
Reviewed by George Staikos.

In "NetworkJob::handleNotifyHeaderReceived", if there are several "Set-Cookie" headers,
we should combine the following ones with the first.

No new test case.

* platform/network/blackberry/NetworkJob.cpp:
(WebCore::NetworkJob::handleNotifyHeaderReceived):

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@132177 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Font’s fast code path is used for partial runs with kerning and ligatures, but shouldn’t be
https://bugs.webkit.org/show_bug.cgi?id=100068

Reviewed by Sam Weinig.

As described in <http://webkit.org/b/100050>, the fast code path doesn’t handle partial runs
correctly when kerning or ligatures are enabled. Since the partial-run case is uncommon,
for now just use the complex code path in this case.

* platform/graphics/Font.cpp:
(WebCore::Font::drawText): Changed to use the complex path for partial runs if there are any
typesetting features.
(WebCore::Font::drawEmphasisMarks): Ditto.
(WebCore::Font::selectionRectForText): Ditto.
(WebCore::Font::offsetForPosition): Changed to use the complex path if there are any
typesetting features.



git-svn-id: http://svn.webkit.org/repository/webkit/trunk@132178 268f45cc-cd09-0410-ab3c-d52691b4dbfc
IndexedDB: Remove custom binding code for IDBCursor.value
https://bugs.webkit.org/show_bug.cgi?id=100034

Reviewed by Kentaro Hara.

Now that we're using ScriptValue instead of SerializedScriptValue we can just expose
IDBCursor.value as an |any| (IDL) or |ScriptValue| (C++) to maintain the specified
semantics that the object identity is retained across accesses.

Test: storage/indexeddb/cursor-value.html

* Modules/indexeddb/IDBCursor.cpp: Remove "dirty" tracking.
(WebCore::IDBCursor::IDBCursor):
(WebCore::IDBCursor::value):
(WebCore::IDBCursor::setValueReady):
* Modules/indexeddb/IDBCursor.h: IDBAny -> ScriptValue
(IDBCursor):
* Modules/indexeddb/IDBCursorWithValue.idl: IDBAny -> any
* Modules/indexeddb/IDBObjectStore.cpp: No need to route through IDBAny to get ScriptValue.
(WebCore):
* UseV8.cmake: Remove references to IDBCustomBindings.cpp
* WebCore.gypi: Ditto.
* WebCore.vcproj/WebCore.vcproj: Ditto.
* bindings/v8/IDBCustomBindings.cpp: Removed.


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@132179 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[EFL] Skip fast/events/tabindex-focus-blur-all.html case.
https://bugs.webkit.org/show_bug.cgi?id=100067

Unreviewed, EFL gardening.

fast/events/tabindex-focus-blur-all.html case has been crashed due to ASSERT in hashtable.
Please refer to BUG 100065 for crash details.

Patch by Kangil Han <kangil.han@samsung.com> on 2012-10-22

* platform/efl-wk1/TestExpectations:

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@132180 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Unreviewed GTK gardening.

Removing failure for an accessibility test that's already passing.
Updating and adding expectations for subpixel tests to reflect
the current situation.

* platform/gtk/TestExpectations:


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@132181 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Make topCallFrame reliable.
https://bugs.webkit.org/show_bug.cgi?id=98928.

Reviewed by Geoffrey Garen.

Source/JavaScriptCore: 

- VM entry points and the GC now uses topCallFrame.
- The callerFrame value in CallFrames are now always the previous
  frame on the stack, except for the first frame which has a
  callerFrame of 0 (not counting the HostCallFrameFlag).
  Hence, we can now traverse every frame on the stack all the way
  back to the first frame.
- GlobalExec's will no longer be used as the callerFrame values in
  call frames.
- Added fences and traps for debugging the JSStack in debug builds.

* bytecode/SamplingTool.h:
(SamplingTool):
(JSC::SamplingTool::CallRecord::CallRecord):
* dfg/DFGOperations.cpp:
- Fixed 2 DFG helper functions to flush topCallFrame as expected.
* dfg/DFGSpeculativeJIT.h:
(JSC::DFG::SpeculativeJIT::prepareForExternalCall):
* interpreter/CallFrame.h:
(JSC::ExecState::callerFrameNoFlags):
(ExecState):
(JSC::ExecState::argIndexForRegister):
(JSC::ExecState::getArgumentUnsafe):
* interpreter/CallFrameClosure.h:
(CallFrameClosure):
* interpreter/Interpreter.cpp:
(JSC):
(JSC::eval):
(JSC::Interpreter::Interpreter):
(JSC::Interpreter::throwException):
(JSC::Interpreter::execute):
(JSC::Interpreter::executeCall):
(JSC::Interpreter::executeConstruct):
(JSC::Interpreter::prepareForRepeatCall):
(JSC::Interpreter::endRepeatCall):
* interpreter/Interpreter.h:
(JSC):
(Interpreter):
* interpreter/JSStack.cpp:
(JSC::JSStack::JSStack):
(JSC::JSStack::gatherConservativeRoots):
(JSC::JSStack::disableErrorStackReserve):
* interpreter/JSStack.h:
(JSC):
(JSStack):
(JSC::JSStack::installFence):
(JSC::JSStack::validateFence):
(JSC::JSStack::installTrapsAfterFrame):
* interpreter/JSStackInlines.h: Added.
(JSC):
(JSC::JSStack::getTopOfFrame):
(JSC::JSStack::getTopOfStack):
(JSC::JSStack::getStartOfFrame):
(JSC::JSStack::pushFrame):
(JSC::JSStack::popFrame):
(JSC::JSStack::generateFenceValue):
(JSC::JSStack::installFence):
(JSC::JSStack::validateFence):
(JSC::JSStack::installTrapsAfterFrame):
* jit/JITStubs.cpp:
(JSC::jitCompileFor):
(JSC::lazyLinkFor):
- Set frame->codeBlock to 0 for both the above because they are called
  with partially intitialized frames (cb uninitialized), but may
  trigger a GC.
(JSC::DEFINE_STUB_FUNCTION):
* runtime/JSGlobalData.cpp:
(JSC::JSGlobalData::JSGlobalData):

LayoutTests: 

- Re-baseline some tests to match the new stack dump results.

* http/tests/inspector/console-resource-errors-expected.txt:
* http/tests/inspector/stacktraces/csp-injected-content-warning-contains-stacktrace-expected.txt:
* http/tests/inspector/stacktraces/csp-inline-warning-contains-stacktrace-expected.txt:



git-svn-id: http://svn.webkit.org/repository/webkit/trunk@132182 268f45cc-cd09-0410-ab3c-d52691b4dbfc
When blocking localStorage, Firefox throws a security exception on access, and maybe so should we
https://bugs.webkit.org/show_bug.cgi?id=63257

Patch by Dan Carney <dcarney@google.com> on 2012-10-23
Reviewed by Jochen Eisinger.

Source/WebCore:

Throw security exception when local storage is accessed
under certain circumstances to match firefox.

No new tests. Existing tests modified.

* bindings/js/JSStorageCustom.cpp:
(WebCore::JSStorage::canGetItemsForName):
(WebCore::JSStorage::nameGetter):
(WebCore::JSStorage::deleteProperty):
(WebCore::JSStorage::getOwnPropertyNames):
* bindings/v8/custom/V8StorageCustom.cpp:
(WebCore):
(WebCore::setDOMException):
(WebCore::V8Storage::namedPropertyEnumerator):
(WebCore::storageGetter):
(WebCore::V8Storage::namedPropertyQuery):
(WebCore::storageDeleter):
* inspector/InspectorDOMStorageAgent.cpp:
(WebCore::InspectorDOMStorageAgent::getDOMStorageEntries):
(WebCore::InspectorDOMStorageAgent::removeDOMStorageItem):
* page/DOMWindow.cpp:
(WebCore::DOMWindow::sessionStorage):
(WebCore::DOMWindow::localStorage):
* storage/Storage.cpp:
* storage/Storage.h:
(WebCore):
(WebCore::Storage::length):
(WebCore::Storage::key):
(WebCore::Storage::getItem):
(WebCore::Storage::setItem):
(WebCore::Storage::removeItem):
(WebCore::Storage::clear):
(WebCore::Storage::contains):
* storage/Storage.idl:
* storage/StorageArea.h:
(StorageArea):
* storage/StorageAreaImpl.cpp:
(WebCore::StorageAreaImpl::canAccessStorage): Checks whether access to storage is a security violation.
(WebCore):
(WebCore::StorageAreaImpl::disabledByPrivateBrowsingInFrame):
(WebCore::StorageAreaImpl::length):
(WebCore::StorageAreaImpl::key):
(WebCore::StorageAreaImpl::getItem):
(WebCore::StorageAreaImpl::setItem):
(WebCore::StorageAreaImpl::removeItem):
(WebCore::StorageAreaImpl::clear):
(WebCore::StorageAreaImpl::contains):
* storage/StorageAreaImpl.h:
(StorageAreaImpl):

Source/WebKit/chromium:

Add security check and security check cache.

* src/StorageAreaProxy.cpp:
(WebCore::StorageAreaProxy::StorageAreaProxy):
(WebCore::StorageAreaProxy::length):
(WebCore::StorageAreaProxy::key):
(WebCore::StorageAreaProxy::getItem):
(WebCore::StorageAreaProxy::setItem):
(WebCore::StorageAreaProxy::removeItem):
(WebCore::StorageAreaProxy::clear):
(WebCore::StorageAreaProxy::contains):
(WebCore::StorageAreaProxy::canAccessStorage):
* src/StorageAreaProxy.h:
(StorageAreaProxy):
(WebCore::StorageAreaProxy::canAccessStorage):

LayoutTests:

Adjust tests to handle new exceptions.

* fast/storage/storage-detached-iframe-expected.txt:
* fast/storage/storage-detached-iframe.html:
* platform/chromium/permissionclient/storage-permission-expected.txt:
* platform/chromium/permissionclient/storage-permission.html:

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@132183 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[EFL][WK2] Compilation warning in GraphicsContext3DPrivate.cpp when AC is enabled
https://bugs.webkit.org/show_bug.cgi?id=99723

Patch by Sudarsana Nagineni <sudarsana.nagineni@intel.com> on 2012-10-23
Reviewed by Kenneth Rohde Christiansen.

Fix compilation warning in GraphicsContext3DPrivate.cpp when AC is
enabled.

No new tests, no change in behavior.

* platform/graphics/efl/GraphicsContext3DPrivate.cpp:
(WebCore::GraphicsContext3DPrivate::createSurface):

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@132184 268f45cc-cd09-0410-ab3c-d52691b4dbfc