Unreviewed. Remove two empty directories.

* public/linuxish: Removed.
* src/linuxish: Removed.


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@122811 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Attempt to fix the Chromium Mac build after <http://trac.webkit.org/changeset/122802>
(https://bugs.webkit.org/show_bug.cgi?id=91451)
 
Remove unused private instance variable AbsoluteQuadsGeneratorContext::m_wasFixed.
This instance variable has remained unused since it was added in
<http://trac.webkit.org/changeset/116718> (https://bugs.webkit.org/show_bug.cgi?id=85725).

I'm unclear as to why the Chromium Mac build began to complain about this
unused instance variable following <http://trac.webkit.org/changeset/122802>, since this
code has been in the tree for a while and we previously instantiated AbsoluteQuadsGeneratorContext
with wasFixed (even though it wasn't used). Regardless, we should remove the unused
instance variable AbsoluteQuadsGeneratorContext::m_wasFixed.

* rendering/RenderInline.cpp:
(WebCore): Remove AbsoluteQuadsGeneratorContext::m_wasFixed.
(WebCore::RenderInline::absoluteQuads):


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@122812 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Introduce ENABLE_CSS_IMAGE_ORIENTATION compile flag
https://bugs.webkit.org/show_bug.cgi?id=89055

Patch by David Barr <davidbarr@chromium.org> on 2012-07-17
Reviewed by Kent Tamura.

The css3-images module is at candidate recommendation.
http://www.w3.org/TR/2012/CR-css3-images-20120417/#the-image-orientation

Add a configuration option for CSS image-orientation support, disabling it by default.

.:

* Source/cmake/WebKitFeatures.cmake:
* Source/cmakeconfig.h.cmake:

Source/JavaScriptCore:

* Configurations/FeatureDefines.xcconfig:

Source/WebKit/mac:

* Configurations/FeatureDefines.xcconfig:

Source/WebKit2:

* Configurations/FeatureDefines.xcconfig:

Tools:

* Scripts/webkitperl/FeatureList.pm:
* qmake/mkspecs/features/features.pri:

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@122813 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[Qt] Unreviewed gardening.

* platform/qt/Skipped:
* platform/qt/fast/sub-pixel/selection/selection-gaps-at-fractional-offsets-expected.txt: Added.

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@122814 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[Forms] Test expectations of datetime/datetime-local/time should not contain milliseconds when they aren't expected
https://bugs.webkit.org/show_bug.cgi?id=91469

Reviewed by Kent Tamura.

This patch gets rid of unexpected millisecond strings from both test
cases and expected text.

This is adaptation of behavior change caused by r119948, introducing
decimal arithmetic, which corrected the expression step mod 1000 used
in BaseDateAndTimeInputType::serialize for checking adding milliseconds
or not, which converts internal date time representation into string.

Before r119948, we used fmod(step, 1000) for this. However, it doesn't
return mathematically correct value when quotient is very large, e.g.
fmod(3.40282346e+38, 1000) returns 616 on x86 linux, although we
expect that it is 0.

* fast/forms/datetime/datetime-stepup-stepdown-from-renderer-expected.txt: Get rid of millig seconds for big step value tests.
* fast/forms/datetime/datetime-stepup-stepdown-from-renderer.html: ditto.
* fast/forms/datetimelocal/datetimelocal-stepup-stepdown-from-renderer-expected.txt: ditto.
* fast/forms/datetimelocal/datetimelocal-stepup-stepdown-from-renderer.html: ditto.
* fast/forms/time/time-stepup-stepdown-from-renderer-expected.txt: Get rid of millig seconds for a big step value test and expected value's fractinal second is zero.
* fast/forms/time/time-stepup-stepdown-from-renderer.html: ditto.

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@122815 268f45cc-cd09-0410-ab3c-d52691b4dbfc
HTMLMediaElement should not use Element::ensureShadowRoot()
https://bugs.webkit.org/show_bug.cgi?id=77936

Reviewed by Hajime Morita.

Source/WebCore:

a video element and an audio element add UserAgentShadowRoot dynamically, and they assume that it's the oldest ShadowRoot.
However an AuthorShadowRoot could be added by a user before a video element and an audio element add UserAgentShadowRoot.
It breaks the assumption that the UserAgentShadowRoot is the oldest.

If the UserAgentShadowRoot is not the oldest, the AuthorShadowRoot a page author added might be ignored.
Since the timing to add UserAgentShadowRoot is not known by a user, the fact that UserAgentShadorRoot is
not the oldest will cause inconsistent behavior.

Adding AuthorShadowRoot to a video element and an audio element is allowed by this patch.

Test: fast/dom/shadow/shadowdom-for-media.html

* dom/ShadowRoot.cpp:
(WebCore::allowsAuthorShadowRoot):
* html/HTMLMediaElement.cpp:
(WebCore::HTMLMediaElement::createShadowSubtree):
(WebCore):
(WebCore::HTMLMediaElement::willAddAuthorShadowRoot):
(WebCore::HTMLMediaElement::createMediaControls):
* html/HTMLMediaElement.h:
(HTMLMediaElement):

LayoutTests:

Adding Shadow DOM to a video element and an audio element is allowed now.

* fast/dom/shadow/shadow-disable-expected.txt:
* fast/dom/shadow/shadow-disable.html:
* fast/dom/shadow/shadowdom-for-media-expected.txt: Added.
* fast/dom/shadow/shadowdom-for-media.html: Added.


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