[CherryPick] Inappropriate validation message for required number/date input elements

[Title] Inappropriate validation message for required number/date input elements
[Issues] N_SE-28998
[Problem] Input type number not showing any error message in Jquery mobile single page application[Solution] Cherry picked.
[Cherry-Picker] Jinwoo Jeong <jw00.jeong@samsung.com>

Inappropriate validation message for required number/date input elements
https://bugs.webkit.org/show_bug.cgi?id=111982

Reviewed by Kentaro Hara.

Source/WebCore:

For validation message, badInput messages should take precedence
over valueMissing messages because users already filled out the
field with a bad value.

Tests: Update fast/forms/validationMessage.html

* html/InputType.cpp:
(WebCore::InputType::validationMessage):
Check badInput first.

LayoutTests:

* fast/forms/validationMessage-expected.txt:
* fast/forms/validationMessage.html:
* platform/chromium/fast/forms/validationMessage-expected.txt:

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

Conflicts:

LayoutTests/ChangeLog
LayoutTests/fast/forms/validationMessage-expected.txt
LayoutTests/fast/forms/validationMessage.html
LayoutTests/platform/chromium/fast/forms/validationMessage-expected.txt
Source/WebCore/ChangeLog

[CherryPick] Implement ValidityState::badInput

[Title] Implement ValidityState::badInput
[Issues] N_SE-28998
[Problem] Input type number not showing any error message in Jquery mobile single page application[Solution] Cherry picked.
[Cherry-Picker] Jinwoo Jeong <jw00.jeong@samsung.com>

Implement ValidityState::badInput
 https://bugs.webkit.org/show_bug.cgi?id=102861

 Reviewed by NOBODY (OOPS!).

 Add ValidityState::badInput, add hasBadInput, which always returns
 false, to FormAssociatedElement, HTMLInputElement, and InputType.

  For NumberInputType, we had hasUnacceptableValue, which was a hack to
  make an input element match to :invalid if the element had non-number
  strings. We don't need the hack any more because badInput affects :invalid
  style. hasUnacceptableValue is re-used for hasBadInput implementation.
  We cleared invalid numbers when elements lost focus to tell users that
  the element had invalid numbers. We don't need this behavior because the
  interactive validation tells it.

  For date/time input types, we should make an input badInput when the
  input has empty value but its sub-fields have values. It covers both of
  partial input cases such as 12/--/2012 and invalid dates such as
  02/31/2012.

  For other types, ValidityState::badInput always returns false.

  This patch doesn't contain tests for badInput validation messages. They
  will be added later.

  Tests: fast/forms/date-multiple-fields/date-multiple-fields-validity-badinput.html
         fast/forms/datetime-multiple-fields/datetime-multiple-fields-validity-badinput.html
         fast/forms/datetimelocal-multiple-fields/datetimelocal-multiple-fields-validity-badinput.html
         fast/forms/month-multiple-fields/month-multiple-fields-validity-badinput.html
         fast/forms/number/number-validity-badinput.html
         fast/forms/time-multiple-fields/time-multiple-fields-validity-badinput.html
         fast/forms/week-multiple-fields/week-multiple-fields-validity-badinput.html

  * html/ValidityState.idl: Add badInput IDL attribute.
  * html/ValidityState.h:
  (ValidityState): Add badInput.
  * html/ValidityState.cpp:
  (WebCore::ValidityState::badInput):
  Added. Calls FormAssociatedElement::hasBadInput.

  * html/FormAssociatedElement.h:
  (FormAssociatedElement): Add hasBadInput.
  * html/FormAssociatedElement.cpp:
  (WebCore::FormAssociatedElement::hasBadInput):
  Added. It always returns false.
  (WebCore::FormAssociatedElement::valid): Takes account of hasBadInput().

  * html/HTMLInputElement.h:
  (HTMLInputElement):
  Remove hasUnacceptableValue, and add hasBadInput override.
  * html/HTMLInputElement.cpp:
  (WebCore::HTMLInputElement::hasBadInput):
  Added. Delegate to InputType::hasBadInput.
  (WebCore): Remove hasUnacceptableValue.

  * html/InputType.h:
  (InputType): Add hasBadInput and badInputText, and remove
  hasUnacceptableValue.
  * html/InputType.cpp:
  (WebCore::InputType::hasBadInput): Added. Returns false.
  (WebCore::InputType::badInputText):
  Added. This function should not be called because hasBadInput always
  returns false.
  (WebCore::InputType::validationMessage):
  Supports badInput. This returns badInputText if hasBadInput is true.

  * html/NumberInputType.h:
  (NumberInputType): Add hasBadInput and badInputTest. Remove
  handleBlurEvent and hasUnacceptableValue.
  * html/NumberInputType.cpp:
  Remove handleBlurEvent, which cleared invalid number strings.
  (WebCore::NumberInputType::hasBadInput):
  Added. We don't need to check existence of a renderer. The standard form
  validation feature doesn't care of it.
  (WebCore::NumberInputType::badInputText): Returns
  validationMessageBadInputForNumberText defined in LocalizedStrings.h.
  * css/SelectorChecker.cpp:
  (WebCore::SelectorChecker::checkOneSelector):
  Remove a hack for hasUnacceptableValue. isValidFormControlElement takes
  account of badInput.
  * dom/Element.h: Remove hasUnacceptableValue.

  * html/BaseMultipleFieldsDateAndTimeInputType.h:
  (BaseMultipleFieldsDateAndTimeInputType): Add hasBadInput and badInputText.
  * html/BaseMultipleFieldsDateAndTimeInputType.cpp:
  (WebCore::BaseMultipleFieldsDateAndTimeInputType::badInputText):
  Returns validationMessageBadInputForDateTimeText defined in LocalizedStrings.h.
  (WebCore::BaseMultipleFieldsDateAndTimeInputType::hasBadInput):
  Added.
  (WebCore::BaseMultipleFieldsDateAndTimeInputType::setValue):
  Add setNeedsValidityCheck call. It is needed because
  updateInnerTextValue can modify subfields empty state.

  * html/TextFieldInputType.cpp:
  (WebCore::TextFieldInputType::subtreeHasChanged): Update a comment.
  * platform/LocalizedStrings.h:
   (WebCore): Add validationMessageBadInputForNumberText and
   validationMessageBadInputForDateTimeText.
   * platform/LocalizedStrings.cpp:
   (WebCore::validationMessageBadInputForNumberText):
   Added a placeholder implementation. This should be fixed later.
   * platform/blackberry/LocalizedStringsBlackBerry.cpp:
   (WebCore::validationMessageBadInputForNumberText): Ditto.
   * platform/efl/LocalizedStringsEfl.cpp:
   (WebCore::validationMessageBadInputForNumberText): Ditto.
   * platform/qt/LocalizedStringsQt.cpp:
   (WebCore::validationMessageBadInputForNumberText): Ditto.

[CherryPick] Refactoring: Move the content of HTMLInputElement::subtreeHasChanged to TextFieldInputType

[Title] Refactoring: Move the content of HTMLInputElement::subtreeHasChanged to TextFieldInputType
[Issues] N_SE-28998
[Problem] Input type number not showing any error message in Jquery mobile single page application
[Solution] Cherry picked.
[Cherry-Picker] Jinwoo Jeong <jw00.jeong@samsung.com>

Refactoring: Move the content of HTMLInputElement::subtreeHasChanged to TextFieldInputType
https://bugs.webkit.org/show_bug.cgi?id=103195

Reviewed by Kentaro Hara.

HTMLInputElement::subtreeHasChanged is called only if the input is
a text field. The code should be moved to TextFieldInputType.

No new tests. This should not change any behavior.

* html/HTMLInputElement.cpp:
- Remove unnecessary NumberInputType.h inclusion.
- Remove convertFromVisibleValue. It was used only by subtreeHasChanged.
(WebCore::HTMLInputElement::subtreeHasChanged):
Move the code to TextFieldInputType::subtreeHasChanged except
calculateAndAdjustDirectionality, which is a protected member of
HTMLElement.
* html/HTMLInputElement.h:
(HTMLInputElement): Remove convertFromVisibleValue.

* html/InputType.cpp:
Move convertFromVisibleValue to TextFieldInputType.
(WebCore::InputType::subtreeHasChanged):
Add ASSERT_NOT_REACHED.
* html/InputType.h:
(InputType): Remove convertFromVisibleValue.

* html/TextFieldInputType.cpp:
(WebCore::TextFieldInputType::convertFromVisibleValue):
Moved from InputType.
(WebCore::TextFieldInputType::subtreeHasChanged):
Moved from HTMLInputElement. A latter part is moved to
didSetValueByUserEdit to be hooked by SearchInputType.
(WebCore::TextFieldInputType::didSetValueByUserEdit):
Moved from HTMLInputElement::subtreeHasChanged, and clean up the code.
* html/TextFieldInputType.h:
(TextFieldInputType):
- Move convertFromVisibleValue from InputType.
- Add didSetValueByUserEdit and subtreeHasChanged.

* html/SearchInputType.cpp:
(WebCore::SearchInputType::didSetValueByUserEdit):
Renamed from subtreeHasChanged, and calls TextFieldInputType::didSetValueByUserEdit.
* html/SearchInputType.h:
(SearchInputType): Rename subtreeHasChanged to didSetValueByUserEdit.

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

Conflicts:

Source/WebCore/ChangeLog

[CherryPick] Correct input[type=number] value sanitization for user-input

[Title] Correct input[type=number] value sanitization for user-input
[Issues] N_SE-28998
[Problem] Input type number not showing any error message in Jquery mobile single page application
[Solution] Cherry picked.
[Cherry-Picker] Jinwoo Jeong <jw00.jeong@samsung.com>

Correct input[type=number] value sanitization for user-input
https://bugs.webkit.org/show_bug.cgi?id=103018

Reviewed by Kentaro Hara.

Source/WebCore:

If a number field has non-number string, HTMLInputElement::value is not
updated and returns the past valid value. It doesn't match to the value
sanitization algorithm defined by the HTML standard [1], and Opera's
behavior. We should sanitize non-number strings to "".

[1] http://www.whatwg.org/specs/web-apps/current-work/multipage/states-of-the-type-attribute.html#number-state-(type=number)
> The value sanitization algorithm is as follows: If the value of the
> element is not a valid floating-point number, then set it to the empty
> string instead.

No new tests. Update existing tests;
fast/forms/number/number-commit-valid-only.html and
fast/forms/number/number-unacceptable-style.html

* html/HTMLInputElement.cpp:
(WebCore::HTMLInputElement::subtreeHasChanged):
Remove isAcceptableValue check.

* html/HTMLInputElement.h:
(HTMLInputElement): isAcceptableValue is no longer needed.
* html/InputType.cpp: Remove isAcceptableValue.
* html/InputType.h: Ditto.
* html/NumberInputType.cpp: Ditto.
(WebCore::NumberInputType::hasUnacceptableValue):
Fold the isAcceptableValue content into this.
* html/NumberInputType.h:
(NumberInputType): Remove isAcceptableValue.

LayoutTests:

* fast/forms/number/number-commit-valid-only-expected.txt:
* fast/forms/number/number-commit-valid-only.html:
Update the expected HTMLInputElement::value results.
* fast/forms/number/number-unacceptable-style-expected.txt:
* fast/forms/number/number-unacceptable-style.html:
Add some checks for HTMLInputElement::value.

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

Conflicts:

LayoutTests/ChangeLog
Source/WebCore/ChangeLog

Conflicts:

Source/WebCore/ChangeLog

Add ewk_web_application_icon_data.h to EWebKit2_HEADERS

[Title] Fix build break on osp-web, wrt, org.tizen.setting
[Issue#]
[Problem] build break on osp-web, wrt, org.tizen.setting
[Cause] ewk_web_application_icon_data.h is missing on EWebKit2_HEADERS
[Solution] add ewk_web_application_icon_data.h to EWebKit2_HEADERS

Change-Id: Ib849976931c82f3264fc322db3079b48f86d4dde

Fixed text selection is cleared when user try to scroll in editable content.

[Title] Fixed text selection is cleared when user try to scroll in editable content.
[Issue#] P130301-2648
[Problem] text selection is cleared when user try to scroll in editable content.
[Cause] There is routine to clear text selection when user try to scroll in editable content.
[Solution] Removed routine to clear text selection when user try to scroll in editable content.
           Added routine to update text selection when scrolling is performed by javascript.

Change-Id: I233a187a4cf1a257bd981e7bb33b0db9c1f2302b

Fix incorrect scroll position adjustment on device rotation

[Title] Fix incorrect scroll position adjustment on device rotation
[issue#] N/A
[Problem] Scroll position moved incorrectly on device rotation
[Cause] By patch d7e58608b9d5f779a796e0459a60849079c10faf, scroll position
        is adjusted by constrainsScrollingToContentEdge
[Solution] Disable constrainsScrollingToContentEdge until viewport attibutes
        change handling

Change-Id: Ica53a9a68e4bb6c4ccfa0b436005bddaa745fd13

[WK2] Fix for white screen on device-orientation change

[Title]  Fix for white screen on device-orientation change
[issue#] N_SE-26272
[Problem] Width and height is not updated in webprocess, when JS querying for it
[Solution] Setting the width and height on view port attributes change
[Developer] prabha.p

Change-Id: I141cf5501d5afa4580d09407f16da04e4ca27566

[Release] Webkit2-efl-123997_0.11.2

Change-Id: I4a9229f079397bd39cc8a14846a2c22f373c09dd

[Cherry-pick] Use -webkit-clip-path shapes to clip HTML elements

[Title] Use -webkit-clip-path shapes to clip HTML elements
[Issues] N/A
[Problem] N/A
[Solution] Cherry picked.
[Cherry-Picker] Sanghyup Lee <sh53.lee@samsung.com>

Use -webkit-clip-path shapes to clip HTML elements
https://bugs.webkit.org/show_bug.cgi?id=95646

Reviewed by Dean Jackson.

Source/WebCore:

-webkit-clip-path creates a new layer for HTML elements now. The border,
background and content gets clipped by the clip path after any filter was
applied.

Tests: css3/masking/clip-path-circle-filter.html
       css3/masking/clip-path-circle-overflow.html
       css3/masking/clip-path-circle-overflow-hidden.html
       css3/masking/clip-path-circle-relative-overflow.html
       css3/masking/clip-path-circle.html
       css3/masking/clip-path-ellipse.html
       css3/masking/clip-path-polygon-evenodd.html
       css3/masking/clip-path-polygon-nonzero.html
       css3/masking/clip-path-polygon.html
       css3/masking/clip-path-rectangle.html

* rendering/RenderBox.h: Create new layer on clip-path.
* rendering/RenderBoxModelObject.h:
(WebCore::RenderBoxModelObject::requiresLayer): Create new layer on clip-path.
* rendering/RenderInline.h:
(WebCore::RenderInline::requiresLayer): Create new layer on clip-path.
* rendering/RenderLayer.cpp: Apply clip-path on context of object.
(WebCore::RenderLayer::paintLayerContents): Create new layer on clip-path.
* rendering/RenderObject.h:
(WebCore::RenderObject::hasClipPath): Indicates that renderer needs to be clipped by clip-path.
* rendering/RenderTableRow.h: Create new layer on clip-path.

LayoutTests:

Added new tests for the -webkit-clip-path property applied to HTML content.

* css3/masking/clip-path-circle-filter.html: Added.
* css3/masking/clip-path-circle-overflow.html: Added.
* css3/masking/clip-path-circle-relative-overflow.html: Added.
* css3/masking/clip-path-circle-overflow-hidden.html: Added.
* css3/masking/clip-path-circle.html: Added.
* css3/masking/clip-path-ellipse.html: Added.
* css3/masking/clip-path-polygon-evenodd.html: Added.
* css3/masking/clip-path-polygon-nonzero.html: Added.
* css3/masking/clip-path-polygon.html: Added.
* css3/masking/clip-path-rectangle.html: Added.
* platform/chromium/TestExpectations:
* platform/efl/TestExpectations:
* platform/gtk/TestExpectations:
* platform/mac/css3/masking/clip-path-circle-expected.png: Added.
* platform/mac/css3/masking/clip-path-circle-expected.txt: Added.
* platform/mac/css3/masking/clip-path-circle-filter-expected.png: Added.
* platform/mac/css3/masking/clip-path-circle-filter-expected.txt: Added.
* platform/mac/css3/masking/clip-path-circle-overflow-expected.png: Added.
* platform/mac/css3/masking/clip-path-circle-overflow-expected.txt: Added.
* platform/mac/css3/masking/clip-path-circle-overflow-hidden-expected.png: Added.
* platform/mac/css3/masking/clip-path-circle-overflow-hidden-expected.txt: Added.
* platform/mac/css3/masking/clip-path-circle-relative-overflow-expected.png: Added.
* platform/mac/css3/masking/clip-path-circle-relative-overflow-expected.txt: Added.
* platform/mac/css3/masking/clip-path-ellipse-expected.png: Added.
* platform/mac/css3/masking/clip-path-ellipse-expected.txt: Added.
* platform/mac/css3/masking/clip-path-polygon-evenodd-expected.png: Added.
* platform/mac/css3/masking/clip-path-polygon-evenodd-expected.txt: Added.
* platform/mac/css3/masking/clip-path-polygon-expected.png: Added.
* platform/mac/css3/masking/clip-path-polygon-expected.txt: Added.
* platform/mac/css3/masking/clip-path-polygon-nonzero-expected.png: Added.
* platform/mac/css3/masking/clip-path-polygon-nonzero-expected.txt: Added.
* platform/mac/css3/masking/clip-path-rectangle-expected.png: Added.
* platform/mac/css3/masking/clip-path-rectangle-expected.txt: Added.

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

Conflicts:

LayoutTests/ChangeLog
LayoutTests/platform/chromium/TestExpectations
LayoutTests/platform/efl/TestExpectations
Source/WebCore/ChangeLog
Source/WebCore/rendering/RenderBox.h
Source/WebCore/rendering/RenderBoxModelObject.h
Source/WebCore/rendering/RenderInline.h
Source/WebCore/rendering/RenderLayer.cpp
Source/WebCore/rendering/RenderTableRow.h

Change-Id: I66be251285f5966180f4b365fdb8342342d691a0

[Cherry-pick] -webkit-clip-path does not apply origin for polygon()

[Title] -webkit-clip-path does not apply origin for polygon()
[Issues] N/A
[Problem] N/A
[Solution] Cherry picked.
[Cherry-Picker] Sanghyup Lee <sh53.lee@samsung.com>

-webkit-clip-path does not apply origin for polygon()
https://bugs.webkit.org/show_bug.cgi?id=95656

Reviewed by Tim Horton.

Source/WebCore:

The polygon() shape function did not apply origin of bouding box on created path. The shape was
not moved to the correct position.

Tests: svg/clip-path/clip-path-shape-polygon-relative-expected.svg
       svg/clip-path/clip-path-shape-polygon-relative.svg

* rendering/style/BasicShapes.cpp:
(WebCore::BasicShapePolygon::path): Apply origin of bounding box.

LayoutTests:

Check that the origin of the bounding box gets applied to the clip path.

* svg/clip-path/clip-path-shape-polygon-relative-expected.svg: Added.
* svg/clip-path/clip-path-shape-polygon-relative.svg: Added.

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

Conflicts:

LayoutTests/ChangeLog
Source/WebCore/ChangeLog

Change-Id: Id302fd04f2856653c8dfdfe52fa5b467856b3f79

[Cherry-pick] Use -webkit-clip-path shapes to clip SVG elements

[Title] Use -webkit-clip-path shapes to clip SVG elements
[Issues] N/A
[Problem] N/A
[Solution] Cherry picked.
[Cherry-Picker] Sanghyup Lee <sh53.lee@samsung.com>

Use -webkit-clip-path shapes to clip SVG elements
https://bugs.webkit.org/show_bug.cgi?id=95620

Reviewed by Rob Buis.

Source/WebCore:

This patch adds a path segment for a BasicShape to a given Path object. This
path and it's wind rule are used to clip the context of the SVG element.

Tests: svg/clip-path/clip-path-shape-circle-1-expected.svg
       svg/clip-path/clip-path-shape-circle-1.svg
       svg/clip-path/clip-path-shape-circle-2-expected.svg
       svg/clip-path/clip-path-shape-circle-2.svg
       svg/clip-path/clip-path-shape-ellipse-1-expected.svg
       svg/clip-path/clip-path-shape-ellipse-1.svg
       svg/clip-path/clip-path-shape-ellipse-2-expected.svg
       svg/clip-path/clip-path-shape-ellipse-2.svg
       svg/clip-path/clip-path-shape-polygon-1-expected.svg
       svg/clip-path/clip-path-shape-polygon-1.svg
       svg/clip-path/clip-path-shape-polygon-2-expected.svg
       svg/clip-path/clip-path-shape-polygon-2.svg
       svg/clip-path/clip-path-shape-polygon-3-expected.svg
       svg/clip-path/clip-path-shape-polygon-3.svg
       svg/clip-path/clip-path-shape-rounded-rect-1-expected.svg
       svg/clip-path/clip-path-shape-rounded-rect-1.svg
       svg/clip-path/clip-path-shape-rounded-rect-2-expected.svg
       svg/clip-path/clip-path-shape-rounded-rect-2.svg

* rendering/style/BasicShapes.cpp: Added helper functions that apply path segments to a given path.
(WebCore::BasicShapeRectangle::path):
(WebCore::BasicShapeCircle::path):
(WebCore::BasicShapeEllipse::path):
(WebCore::BasicShapePolygon::path):
* rendering/style/BasicShapes.h: Make BasicShape virtualized again, since new virtual functions were added.
(WebCore::BasicShape::~BasicShape):
(BasicShape):
(WebCore::BasicShape::windRule): Will return the wind rule of the shape - nonzero by default.
(WebCore::BasicShape::BasicShape):
(BasicShapeRectangle):
(WebCore::BasicShapeRectangle::type): Removed member variable and return type per inheriting class directly.
(WebCore::BasicShapeRectangle::BasicShapeRectangle):
(BasicShapeCircle):
(WebCore::BasicShapeCircle::type): Ditto.
(WebCore::BasicShapeCircle::BasicShapeCircle):
(BasicShapeEllipse):
(WebCore::BasicShapeEllipse::type): Ditto.
(WebCore::BasicShapeEllipse::BasicShapeEllipse):
(BasicShapePolygon):
(WebCore::BasicShapePolygon::windRule):
(WebCore::BasicShapePolygon::type): Ditto.
(WebCore::BasicShapePolygon::BasicShapePolygon):
* rendering/svg/SVGRenderingContext.cpp: If -webkit-clip-path was defined, clip the context to the shape.
Right now -webkit-clip-path overrides clip-path, so that people don't use both at the same time. Current
clip-path property will be replaced, once -webkit-clip-path gets unprefixed.
(WebCore::SVGRenderingContext::prepareToRenderSVGContent):

LayoutTests:

New tests to check behavior of -webkit-clip-path on SVG elements.

* svg/clip-path/clip-path-shape-circle-1-expected.svg: Added.
* svg/clip-path/clip-path-shape-circle-1.svg: Added.
* svg/clip-path/clip-path-shape-circle-2-expected.svg: Added.
* svg/clip-path/clip-path-shape-circle-2.svg: Added.
* svg/clip-path/clip-path-shape-ellipse-1-expected.svg: Added.
* svg/clip-path/clip-path-shape-ellipse-1.svg: Added.
* svg/clip-path/clip-path-shape-ellipse-2-expected.svg: Added.
* svg/clip-path/clip-path-shape-ellipse-2.svg: Added.
* svg/clip-path/clip-path-shape-polygon-1-expected.svg: Added.
* svg/clip-path/clip-path-shape-polygon-1.svg: Added.
* svg/clip-path/clip-path-shape-polygon-2-expected.svg: Added.
* svg/clip-path/clip-path-shape-polygon-2.svg: Added.
* svg/clip-path/clip-path-shape-polygon-3-expected.svg: Added.
* svg/clip-path/clip-path-shape-polygon-3.svg: Added.
* svg/clip-path/clip-path-shape-rounded-rect-1-expected.svg: Added.
* svg/clip-path/clip-path-shape-rounded-rect-1.svg: Added.
* svg/clip-path/clip-path-shape-rounded-rect-2-expected.svg: Added.
* svg/clip-path/clip-path-shape-rounded-rect-2.svg: Added.

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

Conflicts:

LayoutTests/ChangeLog
Source/WebCore/ChangeLog

Change-Id: I0aabeb470a8c5915120a48745bc79747531ba8d3

[Cherry-pick] Introduce new CSS property for clip-path

[Title] Introduce new CSS property for clip-path
[Issues] N/A
[Problem] N/A
[Solution] Cherry picked.
[Cherry-Picker] Sanghyup Lee <sh53.lee@samsung.com>

Introduce new CSS property for clip-path
https://bugs.webkit.org/show_bug.cgi?id=95474

Reviewed by Tim Horton.

Source/WebCore:

This path introduces the new, prefixed CSS property 'clip-path' from the
CSS Masking specification. In a first step the property just accepts
'none' and the the basic shapes from CSS Exclusion. Later it will also be
possible to reference SVG 'clipPath' elements - like Firefox already does.
To enable the parsing of the shapes, the exclusion compiler flags
around the shape parser were removed.

http://dvcs.w3.org/hg/FXTF/raw-file/tip/masking/index.html

Test: fast/masking/parsing-clip-path-shape.html

* css/CSSComputedStyleDeclaration.cpp:
(WebCore::CSSComputedStyleDeclaration::getPropertyCSSValue): Return CSSValue for CSSPropertyWebkitClipPath.
* css/CSSParser.cpp:
(WebCore::CSSParser::parseValue): Add CSSPropertyWebkitClipPath.
(WebCore::CSSParser::parseBasicShape): Modify parser function to accept CSSPropertyWebkitClipPath as well.
* css/CSSParser.h:
* css/CSSProperty.cpp:
(WebCore::CSSProperty::isInheritedProperty):
* css/CSSPropertyNames.in: Added property name -webkit-clip-path.
* css/StyleBuilder.cpp:
(ApplyPropertyClipPath): New property applier just for -webkit-clip-path.
(WebCore::ApplyPropertyClipPath::setValue):
(WebCore::ApplyPropertyClipPath::applyValue):
(WebCore::ApplyPropertyClipPath::createHandler):
(WebCore::StyleBuilder::StyleBuilder):
* rendering/style/RenderStyle.cpp: Repaint if there is a difference between two BasicShapes.
(WebCore::RenderStyle::diff):
* rendering/style/RenderStyle.h:
* rendering/style/StyleRareNonInheritedData.cpp:
(WebCore::StyleRareNonInheritedData::StyleRareNonInheritedData):
(WebCore::StyleRareNonInheritedData::operator==):
(WebCore::StyleRareNonInheritedData::reportMemoryUsage):
* rendering/style/StyleRareNonInheritedData.h: Add new member variable for clip shape.
(StyleRareNonInheritedData):

LayoutTests:

Test parsing behavior of basic shapes on new introduced '-webkit-clip-path' CSS property.

* fast/masking/parsing-clip-path-shape-expected.txt: Added.
* fast/masking/parsing-clip-path-shape.html: Added.

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

Conflicts:

LayoutTests/ChangeLog
Source/WebCore/ChangeLog
Source/WebCore/rendering/style/StyleRareNonInheritedData.cpp

Change-Id: I3c619eabf8c1b4e3243dd1b003d50fe0f7cff1ed

MediaPlayer state has been chagned to pause when player is recieved EOS to avoid playback bugs.

[Title] MediaPlayer state has been chagned to pause when player is recieved EOS to avoid playback bugs.
[Problem] N_SE-28870, N-SE-29806
[Cause] Duration value becomes infinity because playbin state is changed to NULL when player is recieved EOS.
[Solution] Makes player's state to pause when player is recieved EOS.

Change-Id: I1ab5379465d7e5e255ef373e7e7c42197223f1e8

Syncronizing a sound state of audio-session-manager.

[Title] Syncronizing a sound state of audio-session-manager.
[Problem] Audio sound state is not syncronized.
[Cause] Added gst_element_set_state  from upstream
[Solution] Add setSoundState() APIs

Change-Id: Icb66340c702e551c2404474c44ca4d1e2c7b92fe

Video controller's back button is overlapped with forward seek button on fullscreen, WVGA mode.

[Title] Video controller's back button is overlapped with forward seek button on fullscreen, WVGA mode.
[Problem] Video controller's back button is overlapped with forward seek button.
[Cause] CSS setting for mediacontroller doen't consider in WVGA mode.
[Solution] Change CSS values to percentage.

Change-Id: I48ba538fced9bb469fac75bc4be5bdfda893ce2e

[EFL] Remove redundant pipe write to prevent pipe buffer full.
https://bugs.webkit.org/show_bug.cgi?id=101135

Patch by Byungwoo Lee <bw80.lee@samsung.com> on 2012-12-13
Reviewed by Gyuyoung Kim.

To prevent a source of a deadlock, remove the redundant pipe write
in wakeUp() function.

EFL uses ecore_pipe_write() to wake up main run loop, and the function
uses POSIX pipe write with O_NONBLOCK disabled.
With O_NONBLOCK disabled, when written data is more than PIPE_BUF,
pipe write will be blocked until it can be written.

Currently, every wakeUp() function calls ecore_pipe_write() to invoke
wakeUpEvent() callback. And this can make pipe buffer full status
which is the one reason of the lockup problem described in Bug 99494.

* platform/RunLoop.h:
(RunLoop):
* platform/efl/RunLoopEfl.cpp:
(WebCore::RunLoop::RunLoop):
(WebCore::RunLoop::wakeUpEvent):
(WebCore::RunLoop::wakeUp):

Change-Id: I0c46a64d885c929cb2ac265d4b0da020cd3db9a7
git-svn-id: http://svn.webkit.org/repository/webkit/trunk@137580 268f45cc-cd09-0410-ab3c-d52691b4dbfc

[EFL] Use mutex locker in wakeUp() to ensure thread-safety.
https://bugs.webkit.org/show_bug.cgi?id=101132

Patch by Byungwoo Lee <bw80.lee@samsung.com> on 2012-11-28
Reviewed by Gyuyoung Kim.

Add mutex locker for the ecore pipe to ensure thread-safety of
RunLoop::wakeUp().

RunLoop::wakeUp() can be called by multiple thread. It uses
ecore_pipe_write() function but the function is not thread-safe.

* platform/RunLoop.h:
(RunLoop):
* platform/efl/RunLoopEfl.cpp:
(WebCore::RunLoop::wakeUp):

Change-Id: I36bae620af903781cdb3470888aabc434dbdb7b9
git-svn-id: http://svn.webkit.org/repository/webkit/trunk@136006 268f45cc-cd09-0410-ab3c-d52691b4dbfc

Merge "[Cherry-pick] Refactor WrapShape classes to BasicShape" into tizen_2.1

Merge "[Cherry-pick] Refactor WrapShape to Shape/BasicShape" into tizen_2.1

Modify that do not stored drag data in the EFL clipboard, when do drag.

[Title] Modify that do not store drag data in the EFL clipboard, when do drag.
[Issue#] N_SE-28370
[Problem] Should not saved any type of text automatically in clipboard when tap on drag.
[Cause] The drag data is stored in the EFL clipboard.
[Solution] Do not store drag data in the EFL clipbaord.

Change-Id: Ib2140daa4ee46763ce33c81c1bc2d8c1646ea677

[WK2] Support multiple URLs for WebApp meta tag

[Title] Support multiple URLs for WebApp meta tag
[Issue#] N/A
[Problem] Provide a last icon url only
[Cause]
[Solution] Provide an API to get list of icon data which is the set of icon size and urls for WebApp meta tag
- void (*Ewk_Web_App_Icon_URLs_Get_Callback)(Eina_List *icon_urls, void *user_data) is added.
- Ewk_Web_App_Icon_Data type is added.
Following EAPIs are added
- ewk_view_web_application_icon_urls_get()
- ewk_web_application_icon_data_size_get()
- ewk_web_application_icon_data_url_get()

Change-Id: I51076ddf1fcf9dcb919d9a633a74e13436108c52

Merge "Change value of mediaSliderThumHeight" into tizen_2.1

Merge "Change log for Notification" into tizen_2.1

Change value of mediaSliderThumHeight

[Title] Change value of mediaSliderThumHeight
[Problem] MediaPlayer's controller was displayed wrong in emulator.
[Cause] mediaSliderThumbHeight was 0, caculation of rect was wrong.
[Solution] Change mediaSliderThumbHeight

Change-Id: I508e866c604b63b28f4ee9d573708410de3fbf78

Implemented attribute "node" in AudioProcessingEvent

[Title] : Implemented attribute "node" in AudioProcessingEvent
[Issue] : NA
[Problem] : Attribute "node" implementation is not available in WebKit.org
[Solution] : Code changes are implemented for the attribute

Change-Id: I7e9cd9a6dcd97bfed5047bedebd0e5b29636321a

Exception should be thrown when noteOn and noteOff are not called properly

[Title] : Exception should be thrown when noteOn and noteOff are not called properly
[Issue] : TWEB-1091
[Problem] : Exception handling mechanism implementation is not available
[Solution] : Exception handling mechanism is implemented

Change-Id: I92735f97e0df3481f46b06272e2215a7295d4283

Change log for Notification

[Title] Change log for Notification
[Issue#] N/A
[Problem]
[Cause]
[Solution] Print notificationID properly.

Change-Id: I8a820a8e56a964b77e4c745ac31bb1287e078a1b

Separate undo step into insert text and delete text

[Title] Separate undo step into insert text and delete text
[Issue#] P130301-2220
[Problem]
[Cause]
[Solution]

Change-Id: I293da579f96503d23e9cffa3ff0a0e597e531e85

Merge "WebProcess crash is occured during changing default directory path for file system" into tizen_2.1

Merge "Remove ewk_view_use_smart_selection_set() API because it is not used anymore." into tizen_2.1

Merge "Remove ewk_view_top_of_contents_go() because it is not used anymore." into tizen_2.1

Merge "Use EwkView's variables instead of drawingScaleFactor and drawingScrollPosition." into tizen_2.1

Merge "Remove setAccurateVisibleContentsPosition codes because it is not needed anymore." into tizen_2.1

Merge "[Arrange Tizen Local Patch] Remove viewWidth and viewHeight from Setting(Preferences)." into tizen_2.1

Merge "Make TC for ewk_view_feed_touch_event()." into tizen_2.1

WebProcess crash is occured during changing default directory path for file system

[Title] WebProcess crash is occured during changing default directory path for file system
[Problem] Webprocess crash is occured during changing default directory path of file system
[Cause] There are two reasons for this problem.
First, resetStoragePath() method is called before initializeWebProcess
Second, type of m_basePath is class. So if m_basePath can change, it need set API
[Solution] First, LocalFileSystem, web database, web storage initialize themselves in resetStoragePath method even if initializeWebProcess
Add set api for changing m_basePath value

Change-Id: I7a3f9da46f5fab58978623fc2767b633b4501ca0

Remove ewk_view_use_smart_selection_set() API because it is not used anymore.

[Title] Remove ewk_view_use_smart_selection_set() API because it is not used anymore.
[Issue#] N/A
[Problem] ewk_view_use_smart_selection_set() is not used anymore.
[Cause] The ewk_view_use_smart_selection_set() was added for testing desktop web applications,
        but it is not used anymore and smart_selection is default behavior of ewk_view.
        If user want to disable zoom, he/she can set scalable variable to false in the viewport tag of web pages.
[Solution] Remove ewk_view_use_smart_selection_set().

Change-Id: I16dc69f9da1a5a2591428517af99671854c99715

Remove ewk_view_top_of_contents_go() because it is not used anymore.

[Title] Remove ewk_view_top_of_contents_go() because it is not used anymore.
[Issue#] N/A
[Problem] ewk_view_top_of_contents_go() is not used anymore.
[Cause] The ewk_view_top_of_contents_go() was added for old UX concept, but it is not used anymore.
        And browser uses ewk_view_animated_scroll_set() API instead of that.
[Solution] Remove ewk_view_top_of_contents_go().

Change-Id: Id9161c4bd81b8c09f5124194141391431cb378ae

Use EwkView's variables instead of drawingScaleFactor and drawingScrollPosition.

[Title] Use EwkView's variables instead of drawingScaleFactor and drawingScrollPosition.
[Issue#] N/A
[Problem] Refactoring.
[Cause] The drawing variables and EwkView's variables have same role.
        So, I've unified them to use only EwkView's variables.
[Solution] Remove drawingScaleFactor and drawingScrollPosition and refactoring codes.

Change-Id: I5f8105b486c0e1212f76877daed0535552c8b8e9

Remove setAccurateVisibleContentsPosition codes because it is not needed anymore.

[Title] Remove setAccurateVisibleContentsPosition codes because it is not needed anymore.
[Issue#] N/A
[Problem] The setAccurateVisibleContentsPosition codes are not needed anymore.
[Cause] We call the initializeVisibleContentRect() and it set the accurateVisibleContentsPosition by
        calling setVisibleContentRect(), so we don't have to set accurateVisibleContentsPosition separately anymore.
        I know the setAccurateVisibleContentsPosition() is added for fixing N_SE-15113,
        and I've checked that defect does not occur without setAccurateVisibleContentsPosition() codes now.
[Solution] Remove setAccurateVisibleContentsPosition codes.

Change-Id: I6f4ebbe851276d826dede142306691993f10e4be

[Arrange Tizen Local Patch] Remove viewWidth and viewHeight from Setting(Preferences).

[Title] Remove viewWidth and viewHeight from Setting(Preferences).
[Issue#] N/A
[Problem] viewWidth and viewHeight is not used anymore.
[Cause] The codes which use them was removed.
[Solution] Remove viewWidth and viewHeight from Setting(Preferences).

Change-Id: Ifec68ed3bffcde7050c7d45a7eb459f4428472a5

Incorrect display of menu option on a playing video

[Title] Incorret display of menu optionon playing video
[Issue#] WEB-2827
[Problem] Unmute option not displayed after selecting mute
   on a playing video
[Cause] No option unmute was present
[Solution] Added the string unmute for display

Change-Id: Ib2a3cf5a89efeafd8d0f68552e7cdaa01e3b4d2d

Added context menu for input field

[Title] Added context menu for input field
[Issue#] TDIS-2990
[Problem] Unable to paste in input field
[Cause] No context menu items added as its a input filed
[Solution] Added paste item for the context menu

Change-Id: Ie4309c1c770ead5bec444b03906f16491e604d59

Fix find on web pages with -webkit-user-select: none

[Title] Fix find on web pages with -webkit-user-select: none
[Issue#] https://tizendev.org/bugs/browse/N_SE-25811
[Problem] Focus does not change to the matched string on web pages with -webkit-user-select: none
[Cause] frame selection returns NULL on web pages with -webkit-user-select: none and
        current WebKit2 find string algorithm is using the frame selection.
[Solution] Highlight the active matching string using the document's active marker function
           instead of frame selection. For this operation, findString() explictly index
           the current active matching string and scroll to the position.

Change-Id: I498c944c34be3b2c7bd76cd5ad506f7d11cc9b9e

Make TC for ewk_view_feed_touch_event().

[Title] Make TC for ewk_view_feed_touch_event().
[Issue#] N/A
[Problem] TC for ewk_view_feed_touch_event() does not exist.
[Cause] None.
[Solution] Make TC for ewk_view_feed_touch_event().

Change-Id: I9f110aa137dbea982a9b08e3961c7847224b650d

Rename feature that Beep sound when click link

[Title] Rename feature that Beep sound when click link
[Issue#] N/A
[Problem] N/A
[Cause] N/A
[Solution] Rename feature that Beep sound when click link

Change-Id: I3cf37762672020d8714b8dc713595950d11e420e

Conflicts:

Source/WebCore/PlatformTizen.cmake

Implement Beep sound when click link

[Title] Implement Beep sound when click link
[Issue#] N/A
[Problem] N/A
[Cause] N/A
[Solution] Implement Beep sound when click link

Change-Id: I79c1f2cb2b8fc1a075aca4318a881c63c559f68d

Merge "[WK2] Change tizen log for Geolocation" into tizen_2.1

[Cherry-pick] Refactor WrapShape classes to BasicShape

[Title] Refactor WrapShape classes to BasicShape
[Issues] N/A
[Problem] N/A
[Solution] Cherry picked.
[Cherry-Picker] Sanghyup Lee <sh53.lee@samsung.com>

Refactor WrapShape classes to BasicShape
https://bugs.webkit.org/show_bug.cgi?id=95461

Reviewed by Rob Buis.

This is a follow up patch of bug 95411. While the previous patch
just renamed the files, this patch renames the classes, enumerations
and functions.

Just refactoring of internal names. No new tests.

* css/BasicShapeFunctions.cpp:
(WebCore::valueForBasicShape):
(WebCore::basicShapeForValue):
* css/BasicShapeFunctions.h:
(WebCore):
* css/CSSBasicShapes.cpp:
(WebCore::CSSBasicShapeRectangle::cssText):
(WebCore::CSSBasicShapeCircle::cssText):
(WebCore::CSSBasicShapeEllipse::cssText):
(WebCore::CSSBasicShapePolygon::cssText):
* css/CSSBasicShapes.h:
(WebCore::CSSBasicShape::~CSSBasicShape):
(WebCore::CSSBasicShape::CSSBasicShape):
(WebCore::CSSBasicShapeRectangle::create):
(WebCore::CSSBasicShapeRectangle::type):
(WebCore::CSSBasicShapeRectangle::CSSBasicShapeRectangle):
(WebCore::CSSBasicShapeCircle::create):
(WebCore::CSSBasicShapeCircle::type):
(WebCore::CSSBasicShapeCircle::CSSBasicShapeCircle):
(WebCore::CSSBasicShapeEllipse::create):
(WebCore::CSSBasicShapeEllipse::type):
(WebCore::CSSBasicShapeEllipse::CSSBasicShapeEllipse):
(WebCore::CSSBasicShapePolygon::create):
(WebCore::CSSBasicShapePolygon::type):
(WebCore::CSSBasicShapePolygon::CSSBasicShapePolygon):
* css/CSSComputedStyleDeclaration.cpp:
(WebCore::CSSComputedStyleDeclaration::getPropertyCSSValue):
* css/CSSParser.cpp:
(WebCore::CSSParser::parseValue):
(WebCore::CSSParser::parseBasicShapeRectangle):
(WebCore::CSSParser::parseBasicShapeCircle):
(WebCore::CSSParser::parseBasicShapeEllipse):
(WebCore::CSSParser::parseBasicShapePolygon):
(WebCore::CSSParser::parseBasicShape):
* css/CSSParser.h:
(WebCore):
* css/CSSPrimitiveValue.cpp:
(WebCore::CSSPrimitiveValue::init):
* css/CSSPrimitiveValue.h:
(WebCore):
(WebCore::CSSPrimitiveValue::getShapeValue):
(CSSPrimitiveValue):
* css/StyleBuilder.cpp:
(WebCore):
(WebCore::ApplyPropertyWrapShape::setValue):
(WebCore::ApplyPropertyWrapShape::applyValue):
(WebCore::ApplyPropertyWrapShape::createHandler):
* rendering/RenderBlock.cpp:
(WebCore::RenderBlock::updateWrapShapeInfoAfterStyleChange):
* rendering/RenderBlock.h:
(RenderBlock):
* rendering/WrapShapeInfo.cpp:
(WebCore::WrapShapeInfo::isWrapShapeInfoEnabledForRenderBlock):
(WebCore::WrapShapeInfo::computeShapeSize):
* rendering/style/BasicShapes.cpp:
(WebCore::BasicShape::destroy):
* rendering/style/BasicShapes.h:
(WebCore::BasicShape::BasicShape):
(WebCore::BasicShapeRectangle::create):
(WebCore::BasicShapeRectangle::BasicShapeRectangle):
(WebCore::BasicShapeCircle::create):
(WebCore::BasicShapeCircle::BasicShapeCircle):
(WebCore::BasicShapeEllipse::create):
(WebCore::BasicShapeEllipse::BasicShapeEllipse):
(WebCore::BasicShapePolygon::create):
(WebCore::BasicShapePolygon::BasicShapePolygon):
* rendering/style/RenderStyle.h:
* rendering/style/StyleRareNonInheritedData.h:
(StyleRareNonInheritedData):

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

Conflicts:

Source/WebCore/ChangeLog
Source/WebCore/rendering/RenderBlock.cpp
Source/WebCore/rendering/RenderBlock.h
Source/WebCore/rendering/WrapShapeInfo.cpp

[Cherry-pick] Refactor WrapShape to Shape/BasicShape

[Title] Refactor WrapShape to Shape/BasicShape
[Issues] N/A
[Problem] N/A
[Solution] Cherry picked.
[Cherry-Picker] Sanghyup Lee <sh53.lee@samsung.com>

Refactor WrapShape to Shape/BasicShape
https://bugs.webkit.org/show_bug.cgi?id=95411

Reviewed by Andreas Kling.

The wrap shapes are currently specified by CSS3 Exclusions but are useful for other
CSS related proposals like CSS Masking as well. This is the first patch on a chain
of patches to refactor WrapShape to BasicShape. With this patch all relevant files
get renamend and the build systems updated. The classes will be renamend in a second
step.

Just renaming of files. No new tests.

* CMakeLists.txt:
* GNUmakefile.list.am:
* Target.pri:
* WebCore.gypi:
* WebCore.vcproj/WebCore.vcproj:
* WebCore.xcodeproj/project.pbxproj:
* css/BasicShapeFunctions.cpp: Renamed from Source/WebCore/css/WrapShapeFunctions.cpp.
(WebCore):
(WebCore::valueForWrapShape):
(WebCore::convertToLength):
(WebCore::wrapShapeForValue):
* css/BasicShapeFunctions.h: Renamed from Source/WebCore/css/WrapShapeFunctions.h.
(WebCore):
* css/CSSAllInOne.cpp:
* css/CSSBasicShapes.cpp: Renamed from Source/WebCore/css/CSSWrapShapes.cpp.
(WebCore):
(WebCore::CSSWrapShapeRectangle::cssText):
(WebCore::CSSWrapShapeCircle::cssText):
(WebCore::CSSWrapShapeEllipse::cssText):
(WebCore::CSSWrapShapePolygon::cssText):
* css/CSSBasicShapes.h: Renamed from Source/WebCore/css/CSSWrapShapes.h.
(WebCore):
(CSSWrapShape):
(WebCore::CSSWrapShape::~CSSWrapShape):
(WebCore::CSSWrapShape::CSSWrapShape):
(CSSWrapShapeRectangle):
(WebCore::CSSWrapShapeRectangle::create):
(WebCore::CSSWrapShapeRectangle::x):
(WebCore::CSSWrapShapeRectangle::y):
(WebCore::CSSWrapShapeRectangle::width):
(WebCore::CSSWrapShapeRectangle::height):
(WebCore::CSSWrapShapeRectangle::radiusX):
(WebCore::CSSWrapShapeRectangle::radiusY):
(WebCore::CSSWrapShapeRectangle::setX):
(WebCore::CSSWrapShapeRectangle::setY):
(WebCore::CSSWrapShapeRectangle::setWidth):
(WebCore::CSSWrapShapeRectangle::setHeight):
(WebCore::CSSWrapShapeRectangle::setRadiusX):
(WebCore::CSSWrapShapeRectangle::setRadiusY):
(WebCore::CSSWrapShapeRectangle::type):
(WebCore::CSSWrapShapeRectangle::CSSWrapShapeRectangle):
(CSSWrapShapeCircle):
(WebCore::CSSWrapShapeCircle::create):
(WebCore::CSSWrapShapeCircle::centerX):
(WebCore::CSSWrapShapeCircle::centerY):
(WebCore::CSSWrapShapeCircle::radius):
(WebCore::CSSWrapShapeCircle::setCenterX):
(WebCore::CSSWrapShapeCircle::setCenterY):
(WebCore::CSSWrapShapeCircle::setRadius):
(WebCore::CSSWrapShapeCircle::type):
(WebCore::CSSWrapShapeCircle::CSSWrapShapeCircle):
(CSSWrapShapeEllipse):
(WebCore::CSSWrapShapeEllipse::create):
(WebCore::CSSWrapShapeEllipse::centerX):
(WebCore::CSSWrapShapeEllipse::centerY):
(WebCore::CSSWrapShapeEllipse::radiusX):
(WebCore::CSSWrapShapeEllipse::radiusY):
(WebCore::CSSWrapShapeEllipse::setCenterX):
(WebCore::CSSWrapShapeEllipse::setCenterY):
(WebCore::CSSWrapShapeEllipse::setRadiusX):
(WebCore::CSSWrapShapeEllipse::setRadiusY):
(WebCore::CSSWrapShapeEllipse::type):
(WebCore::CSSWrapShapeEllipse::CSSWrapShapeEllipse):
(CSSWrapShapePolygon):
(WebCore::CSSWrapShapePolygon::create):
(WebCore::CSSWrapShapePolygon::appendPoint):
(WebCore::CSSWrapShapePolygon::getXAt):
(WebCore::CSSWrapShapePolygon::getYAt):
(WebCore::CSSWrapShapePolygon::values):
(WebCore::CSSWrapShapePolygon::setWindRule):
(WebCore::CSSWrapShapePolygon::windRule):
(WebCore::CSSWrapShapePolygon::type):
(WebCore::CSSWrapShapePolygon::CSSWrapShapePolygon):
* css/CSSComputedStyleDeclaration.cpp:
* css/CSSParser.cpp:
* css/CSSPrimitiveValue.cpp:
* css/StyleBuilder.cpp:
* rendering/style/BasicShapes.cpp: Renamed from Source/WebCore/rendering/style/WrapShapes.cpp.
(WebCore):
(WebCore::WrapShape::destroy):
* rendering/style/BasicShapes.h: Renamed from Source/WebCore/rendering/style/WrapShapes.h.
(WebCore):
(WrapShape):
(WebCore::WrapShape::deref):
(WebCore::WrapShape::type):
(WebCore::WrapShape::WrapShape):
(WrapShapeRectangle):
(WebCore::WrapShapeRectangle::create):
(WebCore::WrapShapeRectangle::x):
(WebCore::WrapShapeRectangle::y):
(WebCore::WrapShapeRectangle::width):
(WebCore::WrapShapeRectangle::height):
(WebCore::WrapShapeRectangle::cornerRadiusX):
(WebCore::WrapShapeRectangle::cornerRadiusY):
(WebCore::WrapShapeRectangle::setX):
(WebCore::WrapShapeRectangle::setY):
(WebCore::WrapShapeRectangle::setWidth):
(WebCore::WrapShapeRectangle::setHeight):
(WebCore::WrapShapeRectangle::setCornerRadiusX):
(WebCore::WrapShapeRectangle::setCornerRadiusY):
(WebCore::WrapShapeRectangle::WrapShapeRectangle):
(WrapShapeCircle):
(WebCore::WrapShapeCircle::create):
(WebCore::WrapShapeCircle::centerX):
(WebCore::WrapShapeCircle::centerY):
(WebCore::WrapShapeCircle::radius):
(WebCore::WrapShapeCircle::setCenterX):
(WebCore::WrapShapeCircle::setCenterY):
(WebCore::WrapShapeCircle::setRadius):
(WebCore::WrapShapeCircle::WrapShapeCircle):
(WrapShapeEllipse):
(WebCore::WrapShapeEllipse::create):
(WebCore::WrapShapeEllipse::centerX):
(WebCore::WrapShapeEllipse::centerY):
(WebCore::WrapShapeEllipse::radiusX):
(WebCore::WrapShapeEllipse::radiusY):
(WebCore::WrapShapeEllipse::setCenterX):
(WebCore::WrapShapeEllipse::setCenterY):
(WebCore::WrapShapeEllipse::setRadiusX):
(WebCore::WrapShapeEllipse::setRadiusY):
(WebCore::WrapShapeEllipse::WrapShapeEllipse):
(WrapShapePolygon):
(WebCore::WrapShapePolygon::create):
(WebCore::WrapShapePolygon::windRule):
(WebCore::WrapShapePolygon::values):
(WebCore::WrapShapePolygon::getXAt):
(WebCore::WrapShapePolygon::getYAt):
(WebCore::WrapShapePolygon::setWindRule):
(WebCore::WrapShapePolygon::appendPoint):
(WebCore::WrapShapePolygon::WrapShapePolygon):
* rendering/style/StyleRareNonInheritedData.h:

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

Conflicts:

Source/WebCore/ChangeLog
Source/WebCore/Target.pri
Source/WebCore/WebCore.gypi
Source/WebCore/WebCore.xcodeproj/project.pbxproj
Source/WebCore/css/StyleBuilder.cpp

[Release] Webkit2-efl-123997_0.11.1

Change-Id: I779311f693caa83281aebd9ea297ca693c9b222b

Change traversing tree to render tree in screen reader.

[Title] Change traversing tree to render tree in screen reader.
[Issue#] N/A
[Problem]
[Cause]
[Solution]

Change-Id: Ic4c426d8fc0044ca78a13fc0a7e9018a1d5868e2

Checking the clipboard status before appear context menu

[Title] Changed signal for showing text selection handles.
[Issue#] N_SE-29804
[Problem] Context menu options does disappear after clipboard appear
[Cause] There is appear the context menu routine after clipboard appear
[Solution] Checking clipboard status before appear context menu

Change-Id: I8204b0fb2a48272583b20e6f837917cdfdb7d4c5

Switch release branch from master to tizen_2.1

[Title] Switch release branch from master to tizen_2.1
[Issue] N/A
[Problem] Release policy was changed.
[Cause] N/A
[Solution] Switch release branch from master to tizen_2.1.
In addition, removed sdk branch related code because of no needs anymore.

Change-Id: I47aaacd3695f16a8764ac737ef65cfef86ef6747

[WK2] Fix for initial scale handling for mobile pages in UI process side.

[Version]    N/A
[Project]    N/A
[Title]      Fix for issue WEB-2446
[BinType]    N/A
[Customer]   N/A
[Issue#]     WEB-2446
[Problem]    [WK2] Page display differs while reloading the same webpage in "http://dev.bybjorn.com/ipadoffline".
[Cause]      Viewport's initial scale handling on UI process is at fault. In WebKit::PageClientImpl::didChangeContentsSize
             over-writes initilal scale and replaces it with minimumScaleByContentWidth, i.e. ratio of webview (evas object)
             size's width to page contents width. Apparently contents fit to width, instead of initial scale set in pages
             meta viewport tag.
[Solution]   If initialScale is not set explicitly in content's meta viewport and is same to minimumScale, then only
             update initialScale to the minimumScaleByContentWidth. Otherwise retain the initial scale to value specified in
             content's viewport consraints.
[Team]       TiledAC
[Developer]  pritam.nikam
[Request]    N/A
[Horizontal expansion] N/A
[SCMRequest] N/A

Change-Id: Iba9302bb9b0ffa22ea0c5d0e0d6a74c291211d3e

[WK2] Change tizen log for Geolocation

[Title][WK2] Change tizen log for Geolocation
[Issue] N/A
[Problem] A log is unclear.
[Cause] N/A
[Solution] Geolocation should generate console log for accuracy.

Change-Id: I08d18bea74677e1ed1480f8a8db5bc2c338e67ce

Fix keypad issue in google maps

[Title] Fix keypad issue in google maps
[Issue#] N_SE-26103
[Problem] Keypad did not appear in google maps
[Cause] keypad context was reseted before handling tap event
[Solution] Remove keypad context reseting code

Change-Id: Id4e99ea079d0431c89cb7c11fcc0cf5347ad7bda

[CherryPick] [JSC] Remove custom WebAudio mark functions that we can generate instead.

[Title] [CherryPick] [JSC] Remove custom WebAudio mark functions that we can generate instead.
[Issues] N/A
[Problem] WebAudio API Spec update
[Solution] Cherry picked.
[Cherry-Picker] Praveen R Jadhav <praveen.j@samsung.com>

[JSC] Remove custom WebAudio mark functions that we can generate instead.
<http://webkit.org/b/110976>

Reviewed by Eric Carlson.

Remove custom JSC mark functions for AudioContext and ScriptProcessorNode since they
are trivial to generate.

* Modules/webaudio/AudioContext.idl:
* Modules/webaudio/ScriptProcessorNode.idl:
* GNUmakefile.list.am:
* UseJSC.cmake:
* WebCore.xcodeproj/project.pbxproj:
* bindings/js/JSAudioContextCustom.cpp:
* bindings/js/JSScriptProcessorNodeCustom.cpp: Removed.

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

Conflicts:

Source/WebCore/ChangeLog
Source/WebCore/GNUmakefile.list.am
Source/WebCore/Modules/webaudio/AudioContext.idl
Source/WebCore/Modules/webaudio/ScriptProcessorNode.idl
Source/WebCore/WebCore.xcodeproj/project.pbxproj

Change-Id: Ibd2e5227eb150e696182c5b042e95b3690b4f20d

[CherryPick] Regression(r138786): Causes webaudio tests to crash

[Title] [CherryPick] Regression(r138786): Causes webaudio tests to crash
[Issues] N/A
[Problem] WebAudio Intel TCs hang during regression test
[Solution] Cherry picked.
[Cherry-Picker] Praveen R Jadhav <praveen.j@samsung.com>

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

Reviewed by Philippe Normand.

Source/WebCore:

Partially revert r138786 since it causes crashes in webaudio
tests. The WebProcess would actually become unresponsive due
to source element never going to PLAYING state.

Only the changes to webKitWebAudioSrcChangeState() were reverted.

No new tests, already covered by existing tests.

* platform/audio/gstreamer/WebKitWebAudioSourceGStreamer.cpp:
(webKitWebAudioSrcChangeState):

LayoutTests:

Unskip several webaudio tests for EFL WK2 now that the
regression was fixed.

* platform/efl-wk2/TestExpectations:

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

Conflicts:

LayoutTests/ChangeLog
LayoutTests/platform/efl-wk2/TestExpectations
Source/WebCore/ChangeLog

Change-Id: I200bcba74492c4ad5af6b34e2d01b16645683968

Revert "Fix to resolve hang while running WebAudio automation testing."

This reverts commit 6ac5c23f274dbef1454edca6b5cafbdd6003b816.

[Reason]: Updates from WebKit.org https://bugs.webkit.org/show_bug.cgi?id=106182 will be cherry-picked
          to resolve this issue.

Change-Id: If521a91356ca0320dba4a77f7bfb15e8e8e1ddfc

Authentication pop up is displayed even when Authentication credentials are set in request url

[Title] Authentication pop up is displayed even when Authentication credentials are set in request url
[Issue#] DCM-596
[Problem] Even though request url contains Authentication credentials, Authentication pop is being shown.
[Cause] "Authorization" headers is not getting added to the request headers since it is skipped for http family protocols.
[Solution] Adding "Authorization" header to the request in case of http family protocols also.
[Developer] Raveendra Karu (r.karu@samsung.com)

[Release] Webkit2-efl-123997_0.10.83

Change-Id: Ic3c226c7f1ea766e85966180787a52833d57a831

[Cherry-pick] Add a new set of WebKit2 APIs for text search and search results management.

[Title] [Cherry-pick] Add a new set of WebKit2 APIs for text search and search results management.
[Issue] https://tizendev.org/bugs/browse/N_SE-25811
[Problem] Find string is not working in the page with the CSS style, '--webkit-user-select: none'.
[Solution] We need to expand the text search implementation with the new WebKit2 APIs in the open source.
           So I cherry-pick this patch in the open source.
[Cherry-Picker] Jinwoo Song <jinwoo7.song@samsung.com>

Add a new set of WebKit2 APIs for text search and search results management.
https://bugs.webkit.org/show_bug.cgi?id=106834.
<rdar://problem/12597159>

Source/WebCore:

Reviewed by Simon Fraser.

Adding new API to perform text search in WebKit2 without using
the stock UI. The new interface provides all the information
necessary to write a custom UI for search.

Added new TextWebKitAPI test.

* WebCore.exp.in: Added new exported methods.
* editing/Editor.cpp:
(WebCore::Editor::countMatchesForText): Added new parameter to store
all the ranges relative to the matches found.
* editing/Editor.h: Modified the interface of countMatchesForText and removed
the other definition of countMatchesForText with a different signature.
* page/Page.cpp:
(WebCore::Page::findStringMatchingRanges): Added.
(WebCore::Page::markAllMatchesForText): Changed to use the new unified
countMatchesForText.
* page/Page.h:

Source/WebKit/mac:

Reviewed by Simon Fraser.

Adding new API to perform text search in WebKit2 without using
the stock UI. The new interface provides all the information
necessary to write a custom UI for search.

Added new TextWebKitAPI test.

* WebView/WebHTMLView.mm:
(-[WebHTMLView countMatchesForText:inDOMRange:options:limit:markMatches:]):
Modified to reflect the changes to Editor::countMatchesForText interface.

Source/WebKit2:

Reviewed by Simon Fraser.

Adding new API to perform text search in WebKit2 without using
the stock UI. The new interface provides all the information
necessary to write a custom UI for search. The main logic is
implemented in the new functions added to FindController.

Added new TextWebKitAPI test.

* UIProcess/API/C/WKPage.cpp:
(WKPageFindStringMatches): Added.
(WKPageGetImageForFindMatch): Added.
(WKPageSelectFindMatch): Added.
(WKPageSetPageFindMatchesClient): Added.
* UIProcess/API/C/WKPage.h: Added the new API definitions.
* UIProcess/WebFindClient.cpp: Added new client callbacks.
(WebKit::WebFindMatchesClient::didFindStringMatches):
(WebKit::WebFindMatchesClient::didGetImageForMatchResult):
* UIProcess/WebFindClient.h:
(WebFindMatchesClient): Added.
* UIProcess/WebPageProxy.cpp: Added proxy methods.
(WebKit::WebPageProxy::initializeFindMatchesClient):
(WebKit::WebPageProxy::findStringMatches):
(WebKit::WebPageProxy::getImageForFindMatch):
(WebKit::WebPageProxy::selectFindMatch):
(WebKit::WebPageProxy::didGetImageForFindMatch):
(WebKit::WebPageProxy::didFindStringMatches):
* UIProcess/WebPageProxy.h:
* UIProcess/WebPageProxy.messages.in:
* WebProcess/WebPage/FindController.cpp:
(WebKit::FindController::findStringMatches): Finds all the matching
text according to the find options. All the matching text ranges are
stored in a vector until the next call to findStringMatches or until
hideFindUI is called. The message that is sent back to the UI process
contains a vector containing an entry for each find match (i.e. for each
range) and each entry is represented by a vector of the corresponding
text rects. It also returns the index in the vector of matches corresponding
to the first match after the user selection.
If there is no selection the index is always 0 and if there are no
matches after the user selection, the index returned is -1.
(WebKit::FindController::getFindIndicatorBitmapAndRect): Helper function
to share code between updateFindIndicator and getImageForFindMatch.
(WebKit::FindController::getImageForFindMatch): Creates the image corresponding
to the text matched at the given match index.
(WebKit::FindController::selectFindMatch): creates a selection for the range
corresponding to the given match index.
(WebKit::FindController::hideFindUI): Added logic to clear the vector
of matched ranges.
(WebKit::FindController::updateFindIndicator): Updated to use the
new helper function getFindIndicatorBitmapAndRect.
* WebProcess/WebPage/FindController.h:
* WebProcess/WebPage/WebPage.cpp:
(WebKit::WebPage::findStringMatches):
(WebKit::WebPage::getImageForFindMatch):
(WebKit::WebPage::selectFindMatch):
* WebProcess/WebPage/WebPage.h:
* WebProcess/WebPage/WebPage.messages.in:

Tools:

Added new test for the new WebKit2 API for
text search.

Reviewed by Simon Fraser.

* TestWebKitAPI/TestWebKitAPI.xcodeproj/project.pbxproj:
* TestWebKitAPI/Tests/WebKit2/FindMatches.mm: Added.

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

Conflicts:
Source/WebCore/ChangeLog
Source/WebKit/mac/ChangeLog
Source/WebKit2/ChangeLog
Source/WebKit2/UIProcess/WebPageProxy.h
Source/WebKit2/UIProcess/WebPageProxy.messages.in
Source/WebKit2/WebProcess/WebPage/FindController.cpp
Tools/ChangeLog
Tools/TestWebKitAPI/TestWebKitAPI.xcodeproj/project.pbxproj

Change-Id: I50c151a32ebbc2cbaa1ce2c973afb25d7e99db78

Add a enum value for media stream recorder in _Ewk_Extensible_API

[Title] Add a enum value for media stream recorder in _Ewk_Extensible_API
[Problem] Enum type of _Ewk_Extensible_API should be included in the patch (https://tizendev.org/gerrit/#/c/53792/)
[Cause] It missed by mistake.
[Solution] Add a enum value for media stream recorder in _Ewk_Extensible_API

Change-Id: Ieb821df91bd3c7ba8cb0e7a43559ae85c7140560

Remove copyright of error page

[Title]Remove copyright of error page
[Problem] copyright is not needed for this error page.
[Cause] N/A
[Solution] Removed.

Change-Id: Ia65ce85d83a8dab01c21bd0ae60062e7e785b3eb

Merge "Support loading for app:// scheme and widget:// scheme." into tizen_2.1

[Release] Webkit2-efl-123997_0.10.82

Change-Id: Id9d1afa7f841cff33d14e6306c347efca9e9dbb9

Add the check for the setting of form candidate when saving form data

[Title] Add the check for the setting of form candidate when saving form data
[Issue#] N/A
[Problem] form candidate is not working if autofill_password_form is disabled
[Cause] If autofill password is disabled, the form data is not saved
[Solution] Add the check for the setting of form candidate when saving form data

Change-Id: Id17ec873852104732ac447e2fdeaff6a4239df9f

Support loading for app:// scheme and widget:// scheme.

WRT should use protocol for app:// scheme or widget:// scheme.
So we added the new alternativeURL variable to resourceRequestBase class to support app:// and widget:// protocol loading.
Also the changed data:// protocol from file:// protocol is supported.

[Title] Support loading for app:// and widget:// scheme.
[Issue#] N/A
[Problem] The app:// , widget:// protocol is not supported.
[Cause] app:// , widget:// scheme is not supported protocol in webkit.
[Solution] Add the new alternativeURL variable to resourceRequestBase class and if the original url is app:// scheme then replace it to file:// or data:// scheme before request.
[SCMRequest] N/A

Change-Id: I0adf59337a17be36cb65e8ffad13642659fce48a

upload tizen_2.1 source

Change-Id: I18401bc705004db4effe7d86cfe1d5f252ce4a27

sync

Tizen 2.1 base

Initial empty repository