[V8] Replace String::New("symbol") with String::NewSymbol("symbol") (part 2)
https://bugs.webkit.org/show_bug.cgi?id=104082

Reviewed by Adam Barth.

V8 can look up symbols faster than strings.

No tests. No change in behavior.

* bindings/v8/custom/V8ArrayBufferViewCustom.cpp:
(WebCore::getHiddenCopyMethod):
(WebCore::installHiddenCopyMethod):
* bindings/v8/custom/V8ArrayBufferViewCustom.h:
(WebCore::constructWebGLArray):
(WebCore::setWebGLArrayHelper):
* bindings/v8/custom/V8CustomXPathNSResolver.cpp:
(WebCore::V8CustomXPathNSResolver::lookupNamespaceURI):
* bindings/v8/custom/V8DOMWindowCustom.cpp:
(WebCore::DialogHandler::dialogCreated):
(WebCore::DialogHandler::returnValue):
* bindings/v8/custom/V8GeolocationCustom.cpp:
(WebCore::createPositionOptions):
* bindings/v8/custom/V8HTMLDocumentCustom.cpp:
(WebCore::V8HTMLDocument::wrapInShadowObject):
(WebCore::V8HTMLDocument::openCallback):
* bindings/v8/custom/V8HTMLImageElementConstructor.cpp:
(WebCore::V8HTMLImageElementConstructor::GetTemplate):
* bindings/v8/custom/V8SQLTransactionCustom.cpp:
(WebCore::V8SQLTransaction::executeSqlCallback):


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@136645 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Absolutely positioned non-replaced elements should resolve vertical margins against
their containing block's logical width
https://bugs.webkit.org/show_bug.cgi?id=103576

Patch by Bear Travis <betravis@adobe.com> on 2012-12-05
Reviewed by Emil A Eklund.

Source/WebCore:

According to the CSS box model specification, all percentage margin & padding values,
including top & bottom, should be resolved based on the containing block's width.
http://www.w3.org/TR/CSS2/box.html#margin-properties
The writing modes specification has refined this definition to use the containing
block's logical width to resolve percentage margin & padding values.
http://dev.w3.org/csswg/css3-writing-modes/#dimension-mapping

Previously, positioned elements measured their container in the element's block
direction (containerLogicalHeight) to resolve margin-before/after, and in the inline
direction (containerLogicalWidth) to resolve margin-start/end. This patch measures the
container's logical width in its own inline direction (containerRelativeLogicalWidth)
to resolve all margin percentage values.

Test: fast/writing-mode/percentage-margins-absolute.html

* rendering/RenderBox.cpp:
(WebCore::RenderBox::computePositionedLogicalWidthUsing): Calculate the logical width
of the container, and use it to calculate margins.
(WebCore::RenderBox::computePositionedLogicalHeightUsing): Ditto.

LayoutTests:

Test that different writing mode combinations between a parent and child correctly
compute percentage margins for an absolutely positioned child.

* fast/writing-mode/percentage-margins-absolute-expected.txt: Added.
* fast/writing-mode/percentage-margins-absolute.html: Added.

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@136646 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[CSS Exclusions] ExclusionShape inlines should use isFlippedBlocksWritingMode()
https://bugs.webkit.org/show_bug.cgi?id=103939

Patch by Hans Muller <hmuller@adobe.com> on 2012-12-05
Reviewed by Dirk Schulze.

Just a minor cleanup: the protected ExclusionShape inlines, like minYForLogicalLine(),
now use isFlippedBlocksWritingMode() instead of testing for RightToLeftWritingMode directly.
This changeimproves consistency with the rest of WebKit and will work correctly
if "horizontal-bt" writing-mode support is ever added.

No new tests were added since the existing tests cover these methods.

* rendering/ExclusionShape.h:
(WebCore::ExclusionShape::minYForLogicalLine):
(WebCore::ExclusionShape::maxYForLogicalLine):
(WebCore::ExclusionShape::internalToLogicalBoundingBox):

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