Fix the preprocessor guard for ContextMenuItemTagSelectAll in
the implementation of ContextMenuController::contextMenuItemSelected(). The guard was
inconsistent with what is defined in ContextMenuItem.h.

ScriptElement should also be able to keep its Element+CachedScript in
a PendingScript, and then executeScriptSoon can accept a PendingScript.
Once HTMLScriptRunner, ScriptElement, and AsyncScriptRunner all use
PendingScripts, then generic request and execute which operate on
PendingScripts can be factored out to avoid code duplicate that we have.

WebProcess/WebCoreSupport/WebEditorClient.cpp:
(WebKit::WebEditorClient::isContinuousSpellCheckingEnabled):
(WebKit::WebEditorClient::isGrammarCheckingEnabled):
Get the text checking state from the web process.

Although Z_HUFFMAN_ONLY is the fastest on hard-to-compress images,
it is also the slowest, by a wide margin, on easy-to-compress images.
Use a more balanced configuration, based on the libpng compression defaults,
but with a faster compression level (3 instead of 6), and a faster filter
("sub" instead of "all").

A patch to extend compositor to be able to composite into an offscreen texture instead
of just directly to the display buffer. Builds on RenderSurfaceChromium support.
Explicitly resets alpha channel before rendering to display.

WebProcess/WebPage/WebBackForwardListProxy.cpp:
(WebKit::updateBackForwardItem): Added code to encode the back/forward
tree and send it along. The code to decode needs to wait on Brady's
current project.

Do not rely on the GTK+ theme to determine text control borders. This simplifies
the RenderTheme code, prevents metrics differences between GTK+ 2.x and 3.x and
doesn't break the rendering of any theme that I've encountered.

platform/gtk/RenderThemeGtk.cpp:
(WebCore::RenderThemeGtk::adjustSearchFieldStyle): No longer call setTextInputBorders, but
still disable any border radius.

UIProcess/WebProcessProxy.cpp:
(WebKit::WebProcessProxy::updateTextCheckerState):
Send the SetTextCheckerState message to the web process.

UIProcess/mac/TextCheckerMac.mm:
(WebKit::initializeState):
Initialize the state from the user defaults.

(WebKit::TextChecker::state):
Return the state.

(WebKit::TextChecker::setContinuousSpellCheckingEnabled):
(WebKit::TextChecker::setGrammarCheckingEnabled):
(WebKit::TextChecker::setAutomaticSpellingCorrectionEnabled):
Make sure to write the new state.

Fix insertText, setMarkedText and unmarkText methods of
TextInputController to call corresponding methods of WebKit::WebView
rather than WebKit::WebFrame. This change matches the behavior of
chromium browser.
insertText corresponds to WebView::confirmComposition(text)
setMarkedText corresponds to WebView::setComposition(...)
unmarkText corresponds to WebView::confirmComposition()​https://bugs.webkit.org/show_bug.cgi?id=51693

Add WebKit::WebWidget::confirmComposition(const WebString& text)
This new method corresponds to Editor::confirmComposition(text) and
Editor::insertText(text). It'll be used by both DumpRenderTree's
TextInputController and chromium browser.

Fix WebFrameImpl::insertText
It should call Editor::confirmComposition(text) rather than
Editor::insertText(text) if there is an ongoing composition.
It matches the behavior of WebKit Mac port.

Fix WebFrameImpl::setMarkedText
Editor::confirmComposition(text) shouldn't be called in this
method, which incorrectly inserts the text.

Suspend HTMLParserScheduler when page load is deferred to
avoid potential JS re-entrancy. Otherwise, when JS execution is triggered
from an external script or by events, and is blocked by a modal dialog,
WebKit can parse more HTML source and also start another JS execution.

Fix the date recorded in the change log entry for changeset 74973 <​http://trac.webkit.org/changeset/74973>.
It was recorded as "2011-01-03". Instead, it should be "2011-01-04" to correspond
with the date this changeset was committed.

On Symbian PREPEND_INCLUDEPATH is the best way to make sure that WebKit headers
are included before platform headers. On all other platforms continue to use
INCLUDEPATH (as before). This is a continuation of r65877.

Both the Apple Windows and Android ports implement a similar adapter structure,
called ThreadFunctionInvocation and ThreadData respectively, as part of
their thread creation process. Instead, we should share such an adapter
structure and remove duplicate code.

wtf/ThreadingWin.cpp: Moved structure ThreadFunctionInvocation to its own file so that
it can be shared with the Android implementation of createThreadInternal().
(WTF::wtfThreadEntryPoint): Use OwnPtr to hold passed instance of ThreadFunctionInvocation.

Do not kill the web process to force it's termination.
Fix object destruction and cleanup logic and make the cleanup more reliable.
Do not try to cleanup on crash because it is not reliable.

Platform/CoreIPC/qt/ConnectionQt.cpp:
(CoreIPC::Connection::platformInvalidate): Do not delete the socket if we
do not own it. This is the case with a server connection.

Platform/qt/MappedMemoryPool.cpp:
Turn MappedMemoryPool into a QObject so the CleanupHandler can destruct it
in the same way as the other objects.
(WebKit::MappedMemoryPool::instance):
(WebKit::MappedMemoryPool::~MappedMemoryPool):

Platform/qt/SharedMemoryQt.cpp:
(WebKit::SharedMemory::create): No need to care about QCoreApplication::aboutToQuit.
It is handled by the CleanupHandler.
(WebKit::SharedMemory::~SharedMemory): Ditto.

Shared/qt/CleanupHandler.cpp: Renamed from WebKit2/Shared/qt/CrashHandler.cpp.
No longer try to handle crash but just normal termination.
(WebKit::CleanupHandler::CleanupHandler): Connect deleteObjects with QCoreApplication::aboutToQuit.
Ensure appropriate thread affinity.
(WebKit::CleanupHandler::sigTermHandler): Stop the main event loop.
(WebKit::CleanupHandler::deleteObjects): Use deleteLater instead of delete since it is more reliable.

UIProcess/Launcher/qt/ProcessLauncherQt.cpp:
Do not kill the web process immidiately but give it a chance to cleanup.
Use QLocalServer::removeServer for assuring that the socket file will be removed.
(WebKit::ProcessLauncherHelper::serverName):
(WebKit::cleanupAtExit): Renamed from cleanupProcesses. Only kill the web process when it times
out terminating. Fixed the bug of changing the list while iterating it over by disconnecting
from the processStateChanged slot.
(WebKit::QtWebProcess::QtWebProcess): Added missing meta type registration of QProcess::ProcessState.
(WebKit::ProcessLauncherHelper::~ProcessLauncherHelper):
(WebKit::ProcessLauncherHelper::ProcessLauncherHelper): No need to add the the instance to the
CleanupHandler because we will remove the socket file in cleanupAtExit.
(WebKit::ProcessLauncherHelper::instance):
(WebKit::ProcessLauncher::terminateProcess):

platform/graphics/gstreamer/GStreamerGWorld.cpp:
(WebCore::GStreamerGWorld::setWindowOverlay): Use the new xoverlay
API if the GST_CHECK_PLUGINS_BASE_VERSION macro is defined. It was
introduced in same version as the xoverlay API change.

Fix in r74364 was incomplete. When before child is equal to the table part(to
which the new child is getting added), it confuses the table part to add it
incorrectly as an after child. The patch fixes by passing the before child as
the table part's first child.

I'm not the biggest fan of the test_failures or test_results classes,
but it's better to have one shared set of classes, than separate ones
for new vs. old run-webkit-test result handling.

This moves the ORWT results class "LayoutTestResults" over to using
TestResult and TestFailure classes, making it easy for us to
make all our sheriff-bot and other webkitpy code NRWT ready.

This also makes it a trivial patch to generate results.json information
from ORWT results.html files (for flaky test analysis, etc.) as well
as making it a one-liner to report test failure types when the
commit-queue sees flaky tests.

This patch tried not to add new functionality, but only to replace
the guts of LayoutTestResults, while adding unit tests and hoping
not to break anything.

I also moved callers which assumed User.prompt* were static/class methods
to using them as instance methods (since we'll eventually want to make them such).

In the process of re-writing things, I broke the rebaseline command, so I wrote
a unit test to catch my breakage were I do do so again in the future.

css/CSSGradientValue.cpp:
(WebCore::blend): Used to blend colors, which is necessary when truncating
the start of radial gradients.
(WebCore::GradientStop): Small struct to aid gradient stop processing.
(WebCore::CSSGradientValue::addStops): Rename 'positions' to 'stops', and store
the color so that we can blend it when truncating radial gradients. Changed
to handle both linear and radial gradients.
(WebCore::CSSRadialGradientValue::cssText): Update to follow the spec.
(WebCore::CSSRadialGradientValue::resolveRadius): Stylistic change.
(WebCore::distanceToClosestCorner): New utility method.
(WebCore::distanceToFarthestCorner): Ditto.
(WebCore::CSSRadialGradientValue::createGradient): New logic to deal with shape and
fill rules.

css/CSSGradientValue.h:
Add subclasses of CSSGradientValue for linear and radial gradients.

css/CSSGradientValue.cpp:
(WebCore::CSSGradientValue::image): Add FIXME comment about why we can't cache
the gradient sometimes.
(WebCore::compareStops): positions are CSSValues now.
(WebCore::CSSGradientValue::sortStopsIfNeeded): Add assertion that this is only called
for old-style gradients.
(WebCore::CSSGradientValue::addStops): New method that handles the spec rules about
missing positions, ensuring that stop position is ordered, and spacing out stops
without positions. Also normalize gradients which use stops outside the 0-1 range
so that platforms can render them correctly.
(WebCore::positionFromValue): Determin the position on the gradient line for percentage,
number and length values.
(WebCore::CSSGradientValue::computeEndPoint):
(WebCore::CSSLinearGradientValue::cssText):
(WebCore::endPointsFromAngle): Compute endpoints for a gradient which covers the rectangle
given an angle.
(WebCore::CSSLinearGradientValue::createGradient):
(WebCore::CSSRadialGradientValue::cssText):
(WebCore::CSSRadialGradientValue::resolveRadius):
(WebCore::CSSRadialGradientValue::createGradient):

css/CSSParser.cpp:
(WebCore::CSSParser::parseValue): Style fix.
(WebCore::CSSParser::parseContent): Use isGeneratedImageValue() and parseGeneratedImage()
(WebCore::CSSParser::parseFillImage): Use isGeneratedImageValue() and parseGeneratedImage()
(WebCore::CSSParser::parseBorderImage): Use isGeneratedImageValue() and parseGeneratedImage()
(WebCore::parseDeprecatedGradientPoint): Renamed to indicate that it's only used for -webkit-gradient.
(WebCore::parseDeprecatedGradientColorStop): Renamed to indicate that it's only used for -webkit-gradient,
and fixed to store CSSValues for the stop position.
(WebCore::CSSParser::parseDeprecatedGradient): Renamed to indicate that it's only used for -webkit-gradient,
and create CSSLinearGradientValue and CSSRadialGradientValue as appropriate.
(WebCore::valueFromSideKeyword):
(WebCore::parseGradientColorOrKeyword): Color parsing utility.
(WebCore::CSSParser::parseLinearGradient): New method to parse linear gradients.
(WebCore::CSSParser::parseRadialGradient): Stub for new method to parse radial gradients.
(WebCore::CSSParser::isGeneratedImageValue): Detect gradients and CSS canvas.
(WebCore::CSSParser::parseGeneratedImage): Parser for generated images like gradients
and CSS canvas.

css/CSSParser.h:

platform/graphics/Gradient.h:
(WebCore::Gradient::setP0): We need to be able to change the points when normalizing gradients.
(WebCore::Gradient::setP1): Ditto.

Added a way to bind any QObject created as a plugin to JavaScript,
by adding a custom member (qtObject) to WebCore::Widget.
Added a test to tst_qwebpage to make sure plugins created
as QGraphicsWidget are accessible through JavaScript.

Added a way to bind any QObject created as a plugin to JavaScript,
by adding a custom membe to WebCore::Widget.
Added a test to make sure plugins created as QGraphicsWidget are
accessible through JavaScript.

Printing on a page with body { height: 100% } clips out the overflow contents. This happened
because the computePageRects function was never correct. It was using the layer's width and height
for the document's width and height, and the layer no longer includes overflow in its width and
height. It was also incorrectly assuming the first page would begin at (0,0), and this is an invalid
assumption in RTL or vertical text environments.

GNU make ships some superflous built-in rules that we never use
and that end up adding up to a very significant portion of our
total Makefile processing time. Disable them completely by
defining the rule without any recipe, as suggested by the GNU make
manual (10.5.6, Cancelling Implicit Rules).

html/HTMLInputElement.cpp:
(WebCore::HTMLInputElement::HTMLInputElement): Updated for data member
renaming and removal.
(WebCore::HTMLInputElement::isValidValue): Call canSetStringValue
instead of checking specific type numbers.
(WebCore::HTMLInputElement::getAllowedValueStepWithDecimalPlaces):
Use fastGetAttribute and fixed typo in the name of the
scaledStepValueShouldBeInteger function.
(WebCore::HTMLInputElement::isKeyboardFocusable): Call
InputType::isKeyboardFocusable; moved most of the type-specific
logic there.
(WebCore::HTMLInputElement::shouldUseInputMethod): Call
InputType::shouldUseInputMethod; moved the type-specific logic there.
(WebCore::HTMLInputElement::handleBlurEvent): Call
InputType::handleBlurEvent; moved the type-specific logic there.
(WebCore::HTMLInputElement::setType): Tweak the names and types
in this function.
(WebCore::HTMLInputElement::updateType): Removed the code that
set m_deprecatedTypeNumber. Compare types by comparing the value
from formControlType. Removed file-specific logic and instead call
InputType::canChangeFromAnotherType. Streamlined the logic for
activation callbacks.
(WebCore::HTMLInputElement::accessKeyAction): Call
InputType::accessKeyAction; moved the type-specific logic there.
(WebCore::HTMLInputElement::mapToEntry): Call
InputType::shouldRespectHeightAndWidthAttributes and
InputType::shouldRespectAlignAttribute.
(WebCore::HTMLInputElement::parseMappedAttribute): Updated
for name changes and the removal of m_defaultChecked. Changed the
alt attribute logic to be based on the class of the renderer.
Call InputType::srcAttributeChanged and moved the type-specific
logic there. Call shouldRespectAlignAttribute and
shouldRespectHeightAndWidthAttributes rather than having
type-specific logic here. Call minOrMaxAttributeChanged.
(WebCore::HTMLInputElement::rendererIsNeeded): Call
InputType::rendererIsNeeded; moved the type-specific logic there.
(WebCore::HTMLInputElement::attach): Removed the unneeded m_inited
flag, which was redundant with the m_haveType flag. Call
InputType::attach; moved the type-specific logic there.
(WebCore::HTMLInputElement::altText): Use fastGetAttribute.
(WebCore::HTMLInputElement::isSuccessfulSubmitButton): Call
InputType::canBeSuccessfulSubmitButton; moved the type-specific
logic there.
(WebCore::HTMLInputElement::isActivatedSubmit): Updated for
name changes.
(WebCore::HTMLInputElement::setActivatedSubmit): Ditto.
(WebCore::HTMLInputElement::reset): Updated to use
InputType::storesValueSeparateFromAttribute. Also use
hasAttribute(checkedAttr) rather than m_defaultChecked,
since both are the same. Also updated for name change.
(WebCore::HTMLInputElement::setChecked): Updated for name
changes. Also added call to
InputType::shouldSendChangeEventAfterCheckedChanged and
moved the type-specific logic there.
(WebCore::HTMLInputElement::setIndeterminate): Call
isCheckable to see if indeterminate is allowed.
Also updated for name changes.
(WebCore::HTMLInputElement::copyNonAttributeProperties):
Updated for name changes and removed data members.
(WebCore::HTMLInputElement::value): Call
InputType::getTypeSpecificValue and InputType::fallbackValue.
Moved the type-specific logic there.
(WebCore::HTMLInputElement::valueWithDefault): Call
InputType::defaultValue. Moved the type-specific logic there.
(WebCore::HTMLInputElement::setSuggestedValue): Call
InputType::canSetSuggestedValue. Moved the type-specific logic
there.
(WebCore::HTMLInputElement::setValue): Call
InputType::canSetValue. Moved the type-specific logic there.
Clear the file list if it exists rather than checking the
type explicitly. We could probably do that a more elegant way.
(WebCore::HTMLInputElement::placeholder): Use fastGetAttribute.
(WebCore::HTMLInputElement::setValueFromRenderer): Use the
isFileUpload function in the assertion.
(WebCore::HTMLInputElement::setFileListFromRenderer): Put most
of the code from this function into FileInputType::setFileList.
(WebCore::HTMLInputElement::preDispatchEventHandler): Changed
to call InputType::willDispatchClick, which does the type-specific
work. Still need to use a single struct for all types, because
the type of the element could change during the event handling.
(WebCore::HTMLInputElement::postDispatchEventHandler): Changed
to call InputType::didDispatchClick.
(WebCore::HTMLInputElement::defaultValue): Use fastGetAttribute.
(WebCore::HTMLInputElement::accept): Use fastGetAttribute.
(WebCore::HTMLInputElement::alt): Use fastGetAttribute.
(WebCore::HTMLInputElement::src): Use fastGetAttribute.
(WebCore::HTMLInputElement::setAutofilled): Updated for name
changes.
(WebCore::HTMLInputElement::files): Use InputType::files.
(WebCore::HTMLInputElement::isAcceptableValue): Use
InputType::isAcceptableValue.
(WebCore::HTMLInputElement::sanitizeValue): Use
InputType::sanitizeValue.
(WebCore::HTMLInputElement::hasUnacceptableValue): Use
InputType::hasUnacceptableValue.
(WebCore::HTMLInputElement::needsActivationCallback): Use
InputType::shouldResetOnDocumentActivation.
(WebCore::HTMLInputElement::willMoveToNewOwnerDocument): Use
InputType::willMoveToNewOwnerDocument.
(WebCore::HTMLInputElement::dataList): Use
InputType::shouldRespectListAttribute.
(WebCore::HTMLInputElement::selectedOption): Tweaked logic
and naming a bit.
(WebCore::HTMLInputElement::stepUpFromRenderer): Use
fastGetAttribute.
(WebCore::HTMLInputElement::isSpeechEnabled): Use
InputType::shouldRespectSpeechAttribute.
(WebCore::HTMLInputElement::isTextButton): No longer inline.
Calls through to InputType.
(WebCore::HTMLInputElement::isRadioButton): Ditto.
(WebCore::HTMLInputElement::isSearchField): Ditto.
(WebCore::HTMLInputElement::isInputTypeHidden): Ditto.
(WebCore::HTMLInputElement::isPasswordField): Ditto.
(WebCore::HTMLInputElement::isCheckbox): Ditto.
(WebCore::HTMLInputElement::isText): Ditto.
(WebCore::HTMLInputElement::isEmailField): Ditto.
(WebCore::HTMLInputElement::isFileUpload): Ditto.
(WebCore::HTMLInputElement::isImageButton): Ditto.
(WebCore::HTMLInputElement::isNumberField): Ditto.
(WebCore::HTMLInputElement::isSubmitButton): Ditto.
(WebCore::HTMLInputElement::isTelephoneField): Ditto.
(WebCore::HTMLInputElement::isURLField): Ditto.
(WebCore::HTMLInputElement::isEnumeratable): Ditto.
(WebCore::HTMLInputElement::isChecked): No longer inline.
Calls InputType::isCheckable.
(WebCore::HTMLInputElement::hasSpinButton): No longer inline.
Calls through to InputType.
(WebCore::HTMLInputElement::supportsPlaceholder): No longer
inline. Calls isTextType as before, but with no special case
for ISINDEX. That special case was unneeded since it returns
true from isTextType.
(WebCore::HTMLInputElement::checkedRadioButtons): No longer
inline.
(WebCore::HTMLInputElement::handleBeforeTextInsertedEvent):
No longer inline.

html/HTMLInputElement.h: Removed multiple unneeded includes.
The big one is probably InputType.h, but also HTMLFormElement.h.
Removed unneeded forward declarations. Made many functions
no longer inline since they now need to make virtual function
dispatches. Removed the unneeded defaultChecked and
webkitdirectory functions. Both are handled by HTML attribute
reflection for DOM bindings, and the callers instead can get
at the attribute. Made updateCheckedRadioButtons public so it
can be called by an InputType class. Removed
DeprecatedInputType, InputTypeMap, createTypeMap,
deprecatedInputType, allowsIndeterminate,
respectHeightAndWidthAttrs, storesValueSeparateFromAttribute,
m_imageLoader, m_fileList, m_deprecatedTypeNumber,
m_defaultChecked, and m_inited. Renamed m_checked to
m_isChecked, m_useDefaultChecked to m_reflectsCheckedAttribute,
m_indeterminate tom_isIndeterminate, m_haveType to m_hasType,
m_activeSubmit to m_isActivatedSubmit, and m_autofilled to
m_isAutofilled.

html/InputType.h: Removed unneeded ExceptionCode.h include and
used a typedef instead as we do when we want for forward declare it.
Added includes and forward declarations needed for new functions.
Added ClickHandlingState structure. Changed the argument to create
to a String rather than AtomicString. Added many virtual functions.

Update expectations after r74892. A bunch of previously failing tests
now pass (since they match scrollbars with the mac port). Some tests
also started to fail, they should be fixed by removing their
chromium-mac baselines.

EditorClientQt::handleKeyboardEvent relies on QWebPagePrivate::editorActionForKeyEvent()
to handle all editor commands that have a QAction associted with it.
In practice, that covers most of editor commands (as one can see in editorCommandWebActions,
in qwebpage.cpp). However, there are some key down events that are associated to no QAction
or need special handling when features like spatial navigation or
caret browsing are enabled. Currently, these cases are being handled with confusing
and nested if/else switch's statements in EditorClientQt::handleKeyboardEvent(),
and the code is hardly readable.

This patch introduces a mapping hash for those cases, simplifying much
the code. Basically, nested switches statements mixed with if/else's were
refactored, and early returns were added right after an event gets consumed
by the Editor.

Since it is a refactor only patch, there is no funcionality change at
all, and then no new tests are being added.

Originally, the $libraryName is 'JavaScriptCore'. When building release
one, the $libraryDir was 'WebKitBuild/Release/JavaScriptCore/../.libs/'
which doesn't exist anymore ('WebKitBuild/Release/JavaScriptCore'
is 'WebKitBuild/Release/Source/JavaScriptCore' now), and
'WebKitBuild/Release/Source/JavaScriptCore/../../.libs' looks weird,
so make it 'WebKitBuild/Release/.libs'

We now pass the ScriptExecutionContext to window.close so it can find
the Frame and check whether navigation is allowed. This check will
almost always pass because you can only close top-level frames, but the
check will fail when the calling script is sandboxed.

To enforce the sandbox restrictions on History, we need to pass the
ScriptExecutionContext to WebCore. This patch leaves the original
History methods in place because they are used directly by folks who
don't care about security checks.

Test that sandboxed iframes cannot use history to navigate the top
frame. This test is less than ideal, as described in the test itself.
If I was really on top of things, I'd add a test for successful use of
the history API when allow-top-navigation is set, but that test would
be complicated and I'm lazy (enough to copy directly from abarth).

I'm unable to reproduce the failure locally, so this patch is slightly
speculative. We need to be slighly more careful how we compare the
fragment identifiers for Chromium because Chromium uses a URL parser
that is more agressive about canonicalization.

html/HTMLButtonElement.h: Renamed m_activeSubmit to m_isActivatedSubmit
to match the getter function name. The name still doesn't seem great.

html/HTMLFormElement.cpp:
(WebCore::HTMLFormElement::HTMLFormElement): Updated for name changes.
(WebCore::HTMLFormElement::~HTMLFormElement): Use autoComplete function
instead of m_autocomplete data member.
(WebCore::HTMLFormElement::rendererIsNeeded): Use m_wasDemoted data member
instead of otherwise-unused isDemoted function.
(WebCore::HTMLFormElement::submitImplicitly): Updated for name changes.
(WebCore::HTMLFormElement::validateInteractively): Removed code to clear
m_insubmit. This is now handled by the caller, prepareForSubmission.
(WebCore::HTMLFormElement::prepareForSubmission): Renamed. Updated for
name changes. Moved code to clear m_isSubmittingOrPreparingForSubmission
here from validateInteractively. Removed unneeded check of m_doingsubmit
boolean before setting it.
(WebCore::HTMLFormElement::submit): Factored this function into two.
One for JavaScript and one for non-JavaScript. Neither function needs a frame
argument, because the question being asked, anyPageIsProcessingUserGesture,
is a question asked of an entire page group, not a specific frame or page,
so it's not important which is the active frame.
(WebCore::HTMLFormElement::submitFromJavaScript): Ditto.
(WebCore::HTMLFormElement::reset): Updated for name changes.
(WebCore::HTMLFormElement::parseMappedAttribute): Removed code to parse
acceptAttr and got rid of code to set m_autocomplete.
(WebCore::HTMLFormElement::elementForAlias): Changed return type to a raw
pointer.
(WebCore::HTMLFormElement::getNamedElements): Updated to use raw pointer
and the vector find function. Added a FIXME about the comment.
(WebCore::HTMLFormElement::documentDidBecomeActive): Use autoComplete
function instead of m_autocomplete data member.
(WebCore::HTMLFormElement::willMoveToNewOwnerDocument): Ditto.
(WebCore::HTMLFormElement::didMoveToNewOwnerDocument): Ditto.
(WebCore::HTMLFormElement::autoComplete): Ditto.

html/HTMLFormElement.h: Added a FIXME about renaming the autoComplete
function. Renamed prepareSubmit to prepareForSubmission. Got rid of the
frame argument from the submit function and added a new submitFromJavaScript
variant. Removed the unneeded isDemoted function. Changed the return type
of elementForAlias to a raw pointer. Removed m_autocomplete. Renamed
m_insubmit to m_isSubmittingOrPreparingForSubmission, m_doingsubmit to
m_shouldSubmit, m_inreset to m_inResetFunction, m_malformed to m_wasMalformed,
m_demoted to m_wasDemoted. Use plain bool instead of bitfields.

html/HTMLFormElement.idl: Use the function named submitFromJavaScript
instead of using CallWith=DynamicFrame because we don't need to know
what frame is calling. If we did, it's not clear that the "dynamic"
frame would be the right one anyway.

html/HTMLSelectElement.cpp:
(WebCore::HTMLSelectElement::remove): Added an overload that takes an option
element, since the JavaScript binding supports this.

html/HTMLSelectElement.h: Ditto.

html/ImageInputType.cpp:
(WebCore::ImageInputType::handleDOMActivateEvent): Updated for name changes.

Fixes an issue where the style for the associated <img> of an <area>
was passed when considering whether the theme should draw a focus ring
for the <area>. Instead, we should pass the theme the style for the <area>.

It's not possible to test this at this time since there are no themes
that override focus ring drawing for <area>s.

rendering/RenderImage.cpp:
(WebCore::RenderImage::paintFocusRing): Moved call to RenderTheme::supportsFocusRing()
such that it's called with respect to the focused <area>.

Web Inspector: [Chromium] Inspector's tests are very slow on Win(Dbg).

It was a problem with Chromium DRT. DevToolsAgent object instance was
attached not only to the inspected page but to the DevTools window too.
As result all the inspector files were interpreted as a content of inspected page
and were transfered to the DevTools scripts panel for debugging etc.