eea93a1a0598e9c9dd11ff11402945a276c6b954
[WebKit-https.git] / Source / WebKit / blackberry / ChangeLog
1 2012-03-06  Lianghui Chen  <liachen@rim.com>
2
3         [BlackBerry] Remove unused and unneeded WebPageClient::downloadRequested(NetworkRequest&)
4         https://bugs.webkit.org/show_bug.cgi?id=80438
5
6         Reviewed by Antonio Gomes.
7
8         * Api/WebPageClient.h:
9
10 2012-03-06  Jakob Petsovits  <jpetsovits@rim.com>
11
12         [BlackBerry] Don't suspend accel comp when backgrounding a page.
13         https://bugs.webkit.org/show_bug.cgi?id=80369
14         RIM PR: 137609
15
16         Reviewed by Adam Treat.
17
18         Just because the page is in the background doesn't mean
19         it's invisible, doesn't mean it won't have to be redrawn
20         at some point - on rotation, for instance.
21
22         We still suspend accelerated compositing on setVisible(false).
23
24         * Api/WebPage.cpp:
25         (BlackBerry::WebKit::WebPage::notifyPageBackground):
26         (BlackBerry::WebKit::WebPage::notifyPageForeground):
27
28 2012-03-06  Jonathan Dong  <jonathan.dong@torchmobile.com.cn>
29
30         [BlackBerry] function rename issue after MediaPlayerPrivateBlackBerry.[cpp\h] upstream
31         https://bugs.webkit.org/show_bug.cgi?id=80377
32
33         Reviewed by Rob Buis.
34
35         As some of the function names changed in class MediaPlayerPrivate
36         with the upstream of MediaPlayerPrivateBlackBerry.[cpp|h], we
37         should update WebKit/blackberry/Api/WebPage.cpp which uses these
38         functions accordingly.
39         Renamed functions in class MediaPlayerPrivate:
40         windowGet() -> getWindow()
41         windowPositionGet() -> getWindowPosition()
42         mmrContextNameGet() -> mmrContextName()
43
44         * Api/WebPage.cpp:
45         (BlackBerry::WebKit::WebPagePrivate::enterFullscreenForNode):
46
47 2012-03-05  Eli Fidler  <efidler@rim.com>
48
49         The minimum font size WebSetting should actually change the LOGICAL font size in WebCore.
50         https://bugs.webkit.org/show_bug.cgi?id=80312
51         RIM PR: 139874
52
53         Reviewed by George Staikos.
54
55         * Api/WebPage.cpp:
56         (BlackBerry::WebKit::WebPagePrivate::didChangeSettings):
57
58 2012-03-05  Jakob Petsovits  <jpetsovits@rim.com>
59
60         Make accelerated compositing work again with direct rendering.
61         https://bugs.webkit.org/show_bug.cgi?id=80181
62         RIM PR: 139110
63
64         Reviewed by Antonio Gomes.
65         Internally reviewed by Arvid Nilsson.
66
67         The significant amount of refactoring and optimization work
68         that has gone into accelerated compositing missed out on
69         some of the code paths that are being used in direct rendering.
70
71         Animations were relying on blitVisibleContents() only (which
72         is a no-op in direct rendering mode). There were early returns
73         which are suitable to determine whether screen contents need
74         to be updated at all; however, when we're already forcing a
75         re-render then those checks would cause the composition surface
76         not to appear at all, or avoid drawing new animation frames.
77
78         We went through dispatchMessage(), potentially causing
79         mismatches between rendered (but not yet posted) back content
80         and layers composited on top of it. As we're rendering onto
81         the sole target surface (the window) directly and posting
82         from the same thread, we have to wait for compositing on the
83         UI thread to finish before posting the window.
84
85         In turn, this patch combines both drawSubLayers() and
86         blendCompositingSurface() calls into one method, reducing
87         the number of messages to the UI thread within
88         renderDirectToWindow() to one.
89
90         blendCompositingMessage() in renderDirectToScreen() was called
91         with contents coordinates rather than viewport coordinates.
92         That caused some of the composited content to be cut off when
93         the scroll position wasn't (0, 0).
94
95         We called copyPreviousContentsToBackSurfaceOfWindow() twice for
96         one frame, in both renderDirectToWindow() and invalidateWindow().
97         Only one of those (the latter one) is necessary.
98
99         * Api/BackingStore.cpp:
100         (BlackBerry::WebKit::BackingStorePrivate::BackingStorePrivate):
101         (BlackBerry::WebKit::BackingStorePrivate::renderDirectToWindow):
102         (BlackBerry::WebKit::BackingStorePrivate::drawSubLayers):
103         (WebKit):
104         (BlackBerry::WebKit::BackingStorePrivate::drawAndBlendLayersForDirectRendering):
105         * Api/BackingStore.h:
106         (WebKit):
107         * Api/BackingStore_p.h:
108         (BackingStorePrivate):
109         (BlackBerry::WebKit::BackingStorePrivate::isDirectRenderingAnimationMessageScheduled):
110         (BlackBerry::WebKit::BackingStorePrivate::setDirectRenderingAnimationMessageScheduled):
111         * Api/WebPage_p.h:
112         (BlackBerry::WebKit::WebPagePrivate::isAcceleratedCompositingActive):
113         (WebPagePrivate):
114         * WebKitSupport/WebPageCompositor.cpp:
115         (BlackBerry::WebKit::WebPageCompositor::WebPageCompositor):
116         (BlackBerry::WebKit::WebPageCompositor::~WebPageCompositor):
117         (BlackBerry::WebKit::WebPageCompositor::drawLayers):
118         (BlackBerry::WebKit::WebPageCompositor::animationTimerFired):
119         * WebKitSupport/WebPageCompositor.h:
120         (WebPageCompositor):
121
122 2012-03-05  George Staikos  <gstaikos@rim.com>
123
124         [BlackBerry] DOMSupport visibleSelectionForRangeInputElement incorrectly dereferences a null range.
125         https://bugs.webkit.org/show_bug.cgi?id=80274
126
127         Reviewed by Antonio Gomes.
128
129         A null range can be returned so we should not blindly deref it.
130         Reviewed Internally by Mike Fenton.
131
132         * WebKitSupport/DOMSupport.cpp:
133         (BlackBerry::WebKit::DOMSupport::visibleSelectionForRangeInputElement):
134
135 2012-03-04  Jonathan Dong  <jonathan.dong@torchmobile.com.cn>
136
137         [BlackBerry] upstream CredentialManager and CredentialTransformData implementation
138         https://bugs.webkit.org/show_bug.cgi?id=80107
139
140         Reviewed by Antonio Gomes.
141
142         Initial upstream of CredentialManager.[h|cpp] and
143         CredentialTransformData.[h|cpp].
144         No new test.
145
146         * WebCoreSupport/CredentialManager.cpp: Added.
147         (WebCore):
148         (WebCore::CredentialManager::CredentialManager):
149         (WebCore::CredentialManager::autofillAuthenticationChallenge):
150         (WebCore::CredentialManager::autofillPasswordForms):
151         (WebCore::CredentialManager::saveCredentialIfConfirmed):
152         * WebCoreSupport/CredentialManager.h: Added.
153         (WebKit):
154         (WebCore):
155         (CredentialManager):
156         * WebCoreSupport/CredentialTransformData.cpp: Added.
157         (WebCore::CredentialTransformData::CredentialTransformData):
158         (WebCore):
159         (WebCore::CredentialTransformData::url):
160         (WebCore::CredentialTransformData::credential):
161         (WebCore::CredentialTransformData::setCredential):
162         (WebCore::CredentialTransformData::findPasswordFormFields):
163         * WebCoreSupport/CredentialTransformData.h: Added.
164         (WebCore):
165         (CredentialTransformData):
166         (WebCore::CredentialTransformData::isValid):
167         (WebCore::CredentialTransformData::protectionSpace):
168
169 2012-03-04  Antonio Gomes  <agomes@rim.com>
170
171         [BlackBerry] Fixed positioned element not correctly positioned after orientation change, when viewport metatag is used
172         https://bugs.webkit.org/show_bug.cgi?id=80228
173         PR #138865
174
175         Reviewed by George Staikos.
176
177         Viewport size changes in two main scenarios:
178         - orientation changes;
179         - virtual keyboard pop up/hide.
180
181         When we are setting a new viewport size, we need to
182         update the FixedReportedSize of the mainframe. This size
183         is used to return innerWidth|Heigth as well as to calculate
184         the fixed position elements height relative to the RenderView [1].
185
186         [1] RenderBox::containingBlockLogicalHeightForPositioned.
187
188         When we are rotating, we need to delay setting the new FixedReportedSize
189         till we layout and are able to figure out the new contents size. At this
190         time we call setFixedReportedSize, but we do not reposition the fixed elemts
191         afterwards.
192
193         Patch adds a call to FrameView::repaintFixedElementsAfterScrolling, after
194         setting the new size.
195
196         Source/WebKit/blackberry:
197         * Api/WebPage.cpp:
198         (BlackBerry::WebKit::WebPagePrivate::setViewportSize):
199
200 2012-03-02  Mike Fenton  <mifenton@rim.com>
201
202         [BlackBerry] Expose WebInspector state to client and clean up WebSettings
203         https://bugs.webkit.org/show_bug.cgi?id=80177
204
205         Reviewed by Antonio Gomes.
206
207         Expose the Web Inspector state to WebPage client's and
208         re-order initialization of WebSettings to be alphabetical
209         matching their definitions.
210
211         * Api/WebPage.cpp:
212         (BlackBerry::WebKit::WebPage::isWebInspectorEnabled):
213         * Api/WebPage.h:
214         * Api/WebSettings.cpp:
215         (BlackBerry::WebKit::WebSettings::standardSettings):
216
217 2012-03-02  Arvid Nilsson  <anilsson@rim.com>
218
219         Accelerated compositing: Checkerboard never goes away
220         https://bugs.webkit.org/show_bug.cgi?id=79020
221         RIM PR #134164
222
223         Reviewed by Adam Treat.
224
225         Checkerboard appears in accelerated compositing layers when there's no
226         texture for (part of) a layer. The layer renderer queues up some render
227         jobs and schedules a commit to make the WebKit thread process those
228         jobs. Render jobs performed during commit cause texture upload jobs to
229         be scheduled on the UI thread. Texture uploads are performed when next
230         drawing the layers.
231
232         Unfortunately, sometimes commit operation happens without a subsequent
233         call draw the layers.
234
235         In order to implement one-shot drawing sync, I added a call to
236         commitRootLayerIfNeeded() in BackingStore::renderContents(), and
237         I was lucky that most of the time, renderContents() is followed by
238         blit(Visible)Contents() which in turn draws the layers.
239         However, render is not always followed by a blit, for example when
240         rendering offscreen tiles in BackingStore::renderOnIdle(), and in
241         direct rendering mode.
242
243         Fixed by making sure that every call to commitRootLayerIfNeeded() that
244         returns true is followed by a call to drawLayersOnCommit(), unless a
245         blit was requested already.
246
247         Also tweak the logic for one-shot drawing sync to make the code in
248         drawLayersOnCommit() reusable outside of rootLayerCommitTimerFired().
249
250         * Api/BackingStore.cpp:
251         (BlackBerry::WebKit::BackingStorePrivate::BackingStorePrivate):
252         (BlackBerry::WebKit::BackingStorePrivate::renderOnTimer):
253         (BlackBerry::WebKit::BackingStorePrivate::renderOnIdle):
254         (BlackBerry::WebKit::BackingStorePrivate::willFireTimer):
255         (BlackBerry::WebKit::BackingStorePrivate::renderDirectToWindow):
256         (BlackBerry::WebKit::BackingStorePrivate::render):
257         (BlackBerry::WebKit::BackingStorePrivate::blitVisibleContents):
258         (BlackBerry::WebKit::BackingStorePrivate::blitContents):
259         (BlackBerry::WebKit::BackingStorePrivate::renderContents):
260         (WebKit):
261         (BlackBerry::WebKit::BackingStorePrivate::drawLayersOnCommitIfNeeded):
262         * Api/BackingStore_p.h:
263         (BackingStorePrivate):
264         (BlackBerry::WebKit::BackingStorePrivate::willDrawLayersOnCommit):
265
266 2012-03-02  Adam Treat  <atreat@rim.com>
267
268         https://bugs.webkit.org/show_bug.cgi?id=80161
269         PR: 141157
270
271         BlackBerryPlatformScreen.h API has been updated.  Reflect those
272         changes in our usage.
273
274         Reviewed by Antonio Gomes.
275         Internally reviewed by Jakob Petsovits.
276
277         * Api/BackingStore.cpp:
278         (BlackBerry::WebKit::BackingStorePrivate::tileWidth):
279         (BlackBerry::WebKit::BackingStorePrivate::tileHeight):
280         * Api/WebPage.cpp:
281         (BlackBerry::WebKit::WebPagePrivate::init):
282         (BlackBerry::WebKit::WebPagePrivate::transformedViewportSize):
283         (BlackBerry::WebKit::WebPagePrivate::fixedLayoutSize):
284         (BlackBerry::WebKit::WebPagePrivate::recomputeVirtualViewportFromViewportArguments):
285         (BlackBerry::WebKit::WebPagePrivate::setDefaultLayoutSize):
286         (BlackBerry::WebKit::WebPagePrivate::defaultMaxLayoutSize):
287         * WebCoreSupport/FrameLoaderClientBlackBerry.cpp:
288         (WebCore::FrameLoaderClientBlackBerry::restoreViewState):
289         * WebKitSupport/SurfacePool.cpp:
290         (BlackBerry::WebKit::createCompositingSurface):
291
292 2012-03-02  Konrad Piascik  <kpiascik@rim.com>
293
294         [BlackBerry] Set the devicePixelRatio from the results of computeViewportAttributes
295         https://bugs.webkit.org/show_bug.cgi?id=80160
296
297         Reviewed by Antonio Gomes.
298
299         Tested by going to layout test fast/viewport/viewport-95.html and viewport-93.html
300         Previously when executing window.devicePixelRatio these two pages returned 1 now
301         they report the devicePixelRatio returned by computeViewportAttributes.
302
303         * Api/WebPage.cpp:
304         (BlackBerry::WebKit::WebPagePrivate::recomputeVirtualViewportFromViewportArguments):
305
306 2012-03-02  Jacky Jiang  <zhajiang@rim.com>
307
308         Fix a warning in InputHandler::learnText()
309         https://bugs.webkit.org/show_bug.cgi?id=80049
310
311         Reviewed by Antonio Gomes.
312
313         Fix a warning of the comparison "textInField.length() <=
314         MaxLearnTextDataSize" in InputHandler::learnText().
315
316         Rubber-stamped internally by Mike Fenton.
317
318         * WebKitSupport/InputHandler.cpp:
319         (BlackBerry::WebKit::InputHandler::learnText):
320
321 2012-03-01  Andy Chen  <andchen@rim.com>
322
323         [BlackBerry] Implement features for find-in-page
324         https://bugs.webkit.org/show_bug.cgi?id=79820
325
326         Reviewed by Antonio Gomes.
327
328         - Make it be able to search text around the whole page instead of single frame.
329         - Make it be able to start new search from active selection and last active match.
330
331         No new tests as this patch doesn't change behavior.
332
333         * Api/WebPage.cpp:
334         (BlackBerry::WebKit::WebPagePrivate::frameUnloaded):
335         * Api/WebPage_p.h:
336         * WebCoreSupport/FrameLoaderClientBlackBerry.cpp:
337         (WebCore::FrameLoaderClientBlackBerry::dispatchWillClose):
338         (WebCore::FrameLoaderClientBlackBerry::detachedFromParent2):
339         * WebKitSupport/DOMSupport.cpp:
340         (BlackBerry::WebKit::DOMSupport::incrementFrame):
341         * WebKitSupport/DOMSupport.h:
342         * WebKitSupport/InPageSearchManager.cpp:
343         (BlackBerry::WebKit::InPageSearchManager::findNextString):
344         (BlackBerry::WebKit::InPageSearchManager::shouldSearchForText):
345         (BlackBerry::WebKit::InPageSearchManager::findAndMarkText):
346         (BlackBerry::WebKit::InPageSearchManager::setMarkerActive):
347         (BlackBerry::WebKit::InPageSearchManager::frameUnloaded):
348         * WebKitSupport/InPageSearchManager.h:
349         * WebKitSupport/InputHandler.cpp:
350         (BlackBerry::WebKit::InputHandler::frameUnloaded):
351         * WebKitSupport/InputHandler.h:
352
353 2012-03-01  Charles Wei  <charles.wei@torchmobile.com.cn>
354
355         [BlackBerry] Web Notification crashes the browser.
356         https://bugs.webkit.org/show_bug.cgi?id=79897
357
358         Reviewed by Antonio Gomes.
359
360         The reason of the crash is that it still uses the iterator
361         after been removed from the container, which invalidates the
362         iterator. 
363         We should stop processing after we have found the element
364         and removed from the container through the iterator.
365
366         This patch only fixes the crash issue, but not any notification
367         functionality issue, which is tracked seperatly.
368
369         Test case: http://sandbox.gtaero.net/chrome/notifications.php
370
371         * WebCoreSupport/NotificationPresenterImpl.cpp:
372         (WebKit::NotificationPresenterImpl::onPermission):
373         (WebKit::NotificationPresenterImpl::notificationClicked):
374
375 2012-03-01  Mike Fenton  <mifenton@rim.com>
376
377         Autocomplete attribute should apply to textarea's.
378         https://bugs.webkit.org/show_bug.cgi?id=79929
379
380         Reviewed by Antonio Gomes.
381
382         Add local static Qualified name for autocorrect attribute.
383
384         * WebKitSupport/DOMSupport.cpp:
385         (BlackBerry::WebKit::DOMSupport::elementSupportsAutocorrect):
386
387 2012-02-29  Mike Fenton  <mifenton@rim.com>
388
389         Autocomplete attribute should apply to textarea's.
390         https://bugs.webkit.org/show_bug.cgi?id=79929
391
392         Reviewed by Antonio Gomes.
393
394         Allow the autocomplete attribute to bubble back to the form setting.
395
396         Expand support to include checking autocorrect, autocomplete and
397         name/id matching to text areas.
398
399         Reviewed internally by Nima Ghanavatian and Gen Mak.
400
401         * WebKitSupport/DOMSupport.cpp:
402         (BlackBerry::WebKit::DOMSupport::elementSupportsAutocorrect):
403         (BlackBerry::WebKit::DOMSupport::elementSupportsAutocomplete):
404         (BlackBerry::WebKit::DOMSupport::elementAttributeState):
405         * WebKitSupport/DOMSupport.h:
406         * WebKitSupport/InputHandler.cpp:
407         (BlackBerry::WebKit::inputStyle):
408
409 2012-02-29  Max Feil  <mfeil@rim.com>
410
411         [BlackBerry] Add support for FLAC audio and OGG/Vorbis audio
412         https://bugs.webkit.org/show_bug.cgi?id=79519
413
414         Reviewed by Antonio Gomes.
415
416         * Api/WebSettings.cpp:
417         (BlackBerry::WebKit::mimeTypeAssociationMap):
418
419 2012-02-28  Konrad Piascik  <kpiascik@rim.com>
420
421         [BlackBerry] Change the API to use std::string
422         https://bugs.webkit.org/show_bug.cgi?id=79818
423
424         Reviewed by Antonio Gomes.
425
426         * Api/WebPage.cpp:
427         (BlackBerry::WebKit::WebPage::dispatchInspectorMessage):
428         * Api/WebPage.h:
429
430 2012-02-28  Jacky Jiang  <zhajiang@rim.com>
431
432         [BlackBerry] x86 build fix after cleaning up WebPage.cpp
433         https://bugs.webkit.org/show_bug.cgi?id=79814
434
435         Reviewed by Antonio Gomes.
436
437         x86 build fix, keep WebPage::destroyWebPageCompositor() method where it
438         was which was outside of USE(ACCELERATED_COMPOSITING).
439
440         * Api/WebPage.cpp:
441         (BlackBerry::WebKit::WebPage::destroyWebPageCompositor):
442         (WebKit):
443
444 2012-02-28  Mike Fenton  <mifenton@rim.com>
445
446         [BlackBerry] Remove unused focusedNodeChange notifications from the Chrome client.
447         https://bugs.webkit.org/show_bug.cgi?id=79794
448
449         Reviewed by Rob Buis.
450
451         Remove unused notification for focusedNodeChanged.
452
453         Internally reviewed by Gen Mak.
454
455         * Api/WebPageClient.h:
456         * WebCoreSupport/ChromeClientBlackBerry.cpp:
457         (WebCore::ChromeClientBlackBerry::focusedNodeChanged):
458
459 2012-02-27  Jacky Jiang  <zhajiang@rim.com>
460
461         [BlackBerry] Upstream BlackBerry API web page related files
462         https://bugs.webkit.org/show_bug.cgi?id=74380
463
464         Reviewed by Antonio Gomes.
465
466         Clean up WebPage.{h, cpp} and WebPage_p.h.
467         - Remove WebPage::mainFrame() as it is bad to expose WebCore::Frame in
468           the public API, adapt to the change by adding a new method
469           WebPagePrivate::core(Const WebPage*) and expose it to
470           DumpRenderTreeSupport.
471         - Rename WebPage::spellCheckingEnabled to
472           WebPage::setSpellCheckingEnabled.
473         - Remove unused WebPage::focusNodeRect().
474         - Remove extra blank lines.
475         - Put WebPage methods and their associated WebPagePrivate methods
476           together.
477
478         No new tests as this patch doesn't change behavior.
479
480         * Api/WebPage.cpp:
481         (BlackBerry::WebKit::WebPage::WebPage):
482         (WebKit):
483         (BlackBerry::WebKit::WebPage::~WebPage):
484         (BlackBerry::WebKit::WebPagePrivate::core):
485         (BlackBerry::WebKit::WebPage::load):
486         (BlackBerry::WebKit::WebPage::loadExtended):
487         (BlackBerry::WebKit::WebPage::loadFile):
488         (BlackBerry::WebKit::WebPage::download):
489         (BlackBerry::WebKit::WebPage::loadString):
490         (BlackBerry::WebKit::WebPage::executeJavaScript):
491         (BlackBerry::WebKit::WebPage::executeJavaScriptInIsolatedWorld):
492         (BlackBerry::WebKit::WebPage::stopLoading):
493         (BlackBerry::WebKit::WebPage::prepareToDestroy):
494         (BlackBerry::WebKit::WebPage::setScrollPosition):
495         (BlackBerry::WebKit::WebPage::scrollBy):
496         (BlackBerry::WebKit::WebPage::notifyInRegionScrollStatusChanged):
497         (BlackBerry::WebKit::WebPage::zoomToFitScale):
498         (BlackBerry::WebKit::WebPage::initialScale):
499         (BlackBerry::WebKit::WebPage::maximumScale):
500         (BlackBerry::WebKit::WebPage::scrollPosition):
501         (BlackBerry::WebKit::WebPage::viewportSize):
502         (BlackBerry::WebKit::WebPage::activeNodeContext):
503         (BlackBerry::WebKit::WebPage::assignFocus):
504         (BlackBerry::WebKit::WebPage::blockZoomAnimationFinished):
505         (BlackBerry::WebKit::WebPage::onInputLocaleChanged):
506         (BlackBerry::WebKit::WebPage::setScreenOrientation):
507         (BlackBerry::WebKit::WebPage::applyPendingOrientationIfNeeded):
508         (BlackBerry::WebKit::WebPage::setViewportSize):
509         (BlackBerry::WebKit::WebPage::setDefaultLayoutSize):
510         (BlackBerry::WebKit::WebPage::setScrollOriginPoint):
511         (BlackBerry::WebKit::WebPage::textEncoding):
512         (BlackBerry::WebKit::WebPage::forcedTextEncoding):
513         (BlackBerry::WebKit::WebPage::setForcedTextEncoding):
514         (BlackBerry::WebKit::WebPage::setSpellCheckingEnabled):
515         (BlackBerry::WebKit::parentLayer):
516         (BlackBerry::WebKit::WebPagePrivate::inRegionScrollableAreasForPoint):
517         (BlackBerry::WebKit::WebPage::destroyWebPageCompositor):
518         * Api/WebPage.h:
519         (WebCore):
520         (WebKit):
521         * Api/WebPage_p.h:
522         (WebCore):
523         (WebKit):
524         * WebKitSupport/DumpRenderTreeSupport.cpp:
525         (DumpRenderTreeSupport::corePage):
526         (DumpRenderTreeSupport::numberOfPendingGeolocationPermissionRequests):
527         (DumpRenderTreeSupport::resetGeolocationMock):
528         (DumpRenderTreeSupport::setMockGeolocationError):
529         (DumpRenderTreeSupport::setMockGeolocationPermission):
530         (DumpRenderTreeSupport::setMockGeolocationPosition):
531         (DumpRenderTreeSupport::scalePageBy):
532         * WebKitSupport/DumpRenderTreeSupport.h:
533         (WebCore):
534         (DumpRenderTreeSupport):
535
536 2012-02-27  Mike Fenton  <mifenton@rim.com>
537
538         [BlackBerry] Selection handling should be entirely directional
539         https://bugs.webkit.org/show_bug.cgi?id=79692
540
541         Reviewed by Antonio Gomes.
542
543         Make all VisibleSelections directional.
544
545         * WebKitSupport/SelectionHandler.cpp:
546         (BlackBerry::WebKit::SelectionHandler::updateOrHandleInputSelection):
547         (BlackBerry::WebKit::SelectionHandler::setSelection):
548
549 2012-02-27  Ed Baker  <edbaker@rim.com>
550
551         [BlackBerry] Dragging a selection handle outside of the content bounding box does not update the selection range correctly
552         https://bugs.webkit.org/show_bug.cgi?id=78608
553
554         Ensure that when selection handles leave the content bounding box that
555         the handle not being dragged remains fixed. Do not apply padding to a
556         direction that would cause the selection to shrink when performing the
557         handle direction detection.
558
559         Reviewed by Antonio Gomes.
560
561         * WebKitSupport/DOMSupport.cpp:
562         (BlackBerry::WebKit::DOMSupport::convertPointToFrame):
563         * WebKitSupport/DOMSupport.h:
564         * WebKitSupport/SelectionHandler.cpp:
565         (BlackBerry::WebKit::clamp):
566         (BlackBerry::WebKit::directionalVisiblePositionAtExtentOfBox):
567         (BlackBerry::WebKit::SelectionHandler::extendSelectionToFieldBoundary):
568         (BlackBerry::WebKit::SelectionHandler::setSelection):
569         (BlackBerry::WebKit::SelectionHandler::clipPointToVisibleContainer):
570         * WebKitSupport/SelectionHandler.h:
571
572 2012-02-27  Leo Yang  <leo.yang@torchmobile.com.cn>
573
574         [BlackBerry] Upstream accelerated compositing helper class
575         https://bugs.webkit.org/show_bug.cgi?id=78448
576
577         Reviewed by Antonio Gomes.
578
579         Initial upstream, no new tests.
580
581         * WebKitSupport/FrameLayers.cpp: Added.
582         * WebKitSupport/FrameLayers.h: Added.
583
584 2012-02-26  Hajime Morrita  <morrita@chromium.org>
585
586         Move ChromeClient::showContextMenu() to ContextMenuClient
587         https://bugs.webkit.org/show_bug.cgi?id=79427
588
589         Reviewed by Adam Barth.
590
591         * WebCoreSupport/ChromeClientBlackBerry.h:
592         (ChromeClientBlackBerry):
593
594 2012-02-24  Mike Fenton  <mifenton@rim.com>
595
596         [BlackBerry] Eliminate excessive BlackBerry::Platform use in InputHandler
597         https://bugs.webkit.org/show_bug.cgi?id=79393
598
599         Reviewed by Antonio Gomes.
600
601         Cleanup usage of BlackBerry::Platform in InputHandler.
602
603         * WebKitSupport/InputHandler.cpp:
604         (BlackBerry::WebKit::convertStringToWchar):
605         (BlackBerry::WebKit::convertStringToWcharVector):
606         (BlackBerry::WebKit::convertSpannableStringToString):
607         (BlackBerry::WebKit::InputHandler::learnText):
608         (BlackBerry::WebKit::InputHandler::setElementUnfocused):
609         (BlackBerry::WebKit::InputHandler::shouldAcceptInputFocus):
610         (BlackBerry::WebKit::InputHandler::setElementFocused):
611         (BlackBerry::WebKit::InputHandler::nodeTextChanged):
612         (BlackBerry::WebKit::InputHandler::ensureFocusTextElementVisible):
613         (BlackBerry::WebKit::InputHandler::frameUnloaded):
614         (BlackBerry::WebKit::InputHandler::selectionChanged):
615         (BlackBerry::WebKit::InputHandler::setSelection):
616         (BlackBerry::WebKit::InputHandler::handleKeyboardInput):
617         (BlackBerry::WebKit::InputHandler::deleteTextRelativeToCursor):
618         (BlackBerry::WebKit::InputHandler::deleteText):
619         (BlackBerry::WebKit::InputHandler::spannableTextInRange):
620         (BlackBerry::WebKit::InputHandler::setComposingRegion):
621         (BlackBerry::WebKit::InputHandler::finishComposition):
622         (BlackBerry::WebKit::InputHandler::setText):
623         (BlackBerry::WebKit::InputHandler::setTextAttributes):
624         (BlackBerry::WebKit::InputHandler::setRelativeCursorPosition):
625         (BlackBerry::WebKit::InputHandler::setSpannableTextAndRelativeCursor):
626         (BlackBerry::WebKit::InputHandler::setComposingText):
627         (BlackBerry::WebKit::InputHandler::commitText):
628
629 2012-02-24  Mike Fenton  <mifenton@rim.com>
630
631         [BlackBerry] Eliminate excessive BlackBerry::Platform use in SelectionHandler.
632         https://bugs.webkit.org/show_bug.cgi?id=79391
633
634         Reviewed by Antonio Gomes.
635
636         Clean up usage of BlackBerry::Platform in SelectionHandler and
637         explicitly define what namespace to use for ambiguous objects like
638         IntRect and IntPoint.
639
640         * WebKitSupport/SelectionHandler.cpp:
641         (BlackBerry::WebKit::SelectionHandler::cancelSelection):
642         (BlackBerry::WebKit::SelectionHandler::getConsolidatedRegionOfTextQuadsForSelection):
643         (BlackBerry::WebKit::visiblePositionForPointIgnoringClipping):
644         (BlackBerry::WebKit::directionOfPointRelativeToRect):
645         (BlackBerry::WebKit::SelectionHandler::shouldUpdateSelectionOrCaretForPoint):
646         (BlackBerry::WebKit::SelectionHandler::setCaretPosition):
647         (BlackBerry::WebKit::directionalVisiblePositionAtExtentOfBox):
648         (BlackBerry::WebKit::pointIsOutsideOfBoundingBoxInDirection):
649         (BlackBerry::WebKit::SelectionHandler::extendSelectionToFieldBoundary):
650         (BlackBerry::WebKit::SelectionHandler::updateOrHandleInputSelection):
651         (BlackBerry::WebKit::SelectionHandler::clipPointToFocusNode):
652         (BlackBerry::WebKit::SelectionHandler::setSelection):
653         (BlackBerry::WebKit::SelectionHandler::selectAtPoint):
654         (BlackBerry::WebKit::SelectionHandler::selectObject):
655         (BlackBerry::WebKit::comparePointsToReferencePoint):
656         (BlackBerry::WebKit::minXMinYCorner):
657         (BlackBerry::WebKit::maxXMinYCorner):
658         (BlackBerry::WebKit::minXMaxYCorner):
659         (BlackBerry::WebKit::maxXMaxYCorner):
660         (BlackBerry::WebKit::caretLocationForRect):
661         (BlackBerry::WebKit::caretComparisonPointForRect):
662         (BlackBerry::WebKit::adjustCaretRects):
663         (BlackBerry::WebKit::SelectionHandler::clipRegionToVisibleContainer):
664         (BlackBerry::WebKit::referencePoint):
665         (BlackBerry::WebKit::SelectionHandler::selectionPositionChanged):
666         (BlackBerry::WebKit::SelectionHandler::caretPositionChanged):
667         (BlackBerry::WebKit::SelectionHandler::selectionContains):
668
669 2012-02-24  Shinya Kawanaka  <shinyak@chromium.org>
670
671         SpellCheckRequest needs to know the context where the spellcheck happened.
672         https://bugs.webkit.org/show_bug.cgi?id=79320
673
674         Reviewed by Hajime Morita.
675
676         * WebCoreSupport/EditorClientBlackBerry.cpp:
677         (WebCore::EditorClientBlackBerry::requestCheckingOfString):
678         * WebCoreSupport/EditorClientBlackBerry.h:
679         (EditorClientBlackBerry):
680
681 2012-02-24  Charles Wei  <charles.wei@torchmobile.com.cn>
682
683         [BlackBerry] Anchor mailto: with target set won't launch Messaging application when clicked
684         https://bugs.webkit.org/show_bug.cgi?id=79318
685
686         Need to give the client a chance to decide how to handle the new window request.
687
688         Reviewed by Rob Buis.
689
690         * WebCoreSupport/FrameLoaderClientBlackBerry.cpp:
691         (WebCore::FrameLoaderClientBlackBerry::dispatchDecidePolicyForNewWindowAction):
692
693 2012-02-23  Mike Fenton  <mifenton@rim.com>
694
695         [BlackBerry] Selection handler has compile failure with logs enabled.
696         https://bugs.webkit.org/show_bug.cgi?id=79392
697
698         Reviewed by Antonio Gomes.
699
700         Build Fix.  Update log to avoid usage of toString which was removed.
701
702         * WebKitSupport/SelectionHandler.cpp:
703         (BlackBerry::WebKit::SelectionHandler::selectionPositionChanged):
704
705 2012-02-19  Antonio Gomes  <agomes@rim.com>
706
707         Fat fingers - Add a clearer way to distinguish the node we want (shadow or non-shadow)
708         https://bugs.webkit.org/show_bug.cgi?id=79256
709         PR #127814 / MKS_2587410
710
711         Reviewed by Rob Buis.
712
713         Patch adds a cleaner way for call sites of FatFingersResult to
714         query for the appropriated target node: shadow or non-shadow DOM nodes.
715
716         It also renames FatFingersResults::validNode to ::node, assuming
717         that "invalid" nodes are not applicable in any context.
718
719         * Api/WebPage.cpp:
720         (BlackBerry::WebKit::WebPagePrivate::clearDocumentData):
721         (BlackBerry::WebKit::WebPagePrivate::contextNode):
722         (BlackBerry::WebKit::WebPagePrivate::handleMouseEvent):
723         * WebKitSupport/FatFingers.h:
724         (FatFingersResult):
725         (BlackBerry::WebKit::FatFingersResult::node):
726         (BlackBerry::WebKit::FatFingersResult::nodeAsElementIfApplicable):
727         * WebKitSupport/SelectionHandler.cpp:
728         (BlackBerry::WebKit::SelectionHandler::selectAtPoint):
729         * WebKitSupport/TouchEventHandler.cpp:
730         (BlackBerry::WebKit::TouchEventHandler::touchHoldEvent):
731         (BlackBerry::WebKit::TouchEventHandler::handleTouchPoint):
732
733 2012-02-23  Jacky Jiang  <zhajiang@rim.com>
734
735         [BlackBerry] Upstream BlackBerry API web page related files
736         https://bugs.webkit.org/show_bug.cgi?id=74380
737
738         Reviewed by Antonio Gomes.
739
740         Initial upstream, no new tests.
741
742         * Api/WebPage.cpp: Added.
743         * Api/WebPage.h: Added.
744         * Api/WebPage_p.h: Added.
745
746 2012-02-23  Leo Yang  <leo.yang@torchmobile.com.cn>
747
748         [BlackBerry] Remove unused ChromeClientBlackBerry::platformCompositingWindow(), platformWindow() and WebPageClient::compositingWindow()
749         https://bugs.webkit.org/show_bug.cgi?id=78681
750
751         Reviewed by Antonio Gomes.
752
753         * Api/WebPageClient.h:
754         * WebCoreSupport/ChromeClientBlackBerry.cpp:
755         (WebCore):
756         * WebCoreSupport/ChromeClientBlackBerry.h:
757         (ChromeClientBlackBerry):
758
759 2012-02-23  Leo Yang  <leo.yang@torchmobile.com.cn>
760
761         [BlackBerry] Upstream GLES2Context.{h, cpp}
762         https://bugs.webkit.org/show_bug.cgi?id=79196
763
764         Reviewed by Rob Buis.
765
766         Initial upstream, no new tests.
767
768         * WebKitSupport/GLES2Context.cpp: Added.
769         * WebKitSupport/GLES2Context.h: Added.
770
771 2012-02-23  Mike Fenton  <mifenton@rim.com>
772
773         [BlackBerry] InputHandler requires cleanup of Navigation Mode handling.
774         https://bugs.webkit.org/show_bug.cgi?id=79366
775
776         Reviewed by Rob Buis.
777
778         Cleanup InputHandler navigation based code.
779
780         1) Remove the concept of NavigationMode and replace it
781            with simple showKeyboard calls.
782
783         2) Remove navigation move events and replace with standard
784            key events.
785
786         3) Standardize function/variable names and remove obsolete
787            functions.
788
789         * Api/WebPageClient.h:
790         * WebKitSupport/InputHandler.cpp:
791         (BlackBerry::WebKit::InputHandler::InputHandler):
792         (BlackBerry::WebKit::InputHandler::nodeFocused):
793         (BlackBerry::WebKit::InputHandler::setElementUnfocused):
794         (BlackBerry::WebKit::InputHandler::setElementFocused):
795         (BlackBerry::WebKit::InputHandler::ensureFocusTextElementVisible):
796         (BlackBerry::WebKit::InputHandler::setDelayKeyboardVisibilityChange):
797         (BlackBerry::WebKit::InputHandler::processPendingKeyboardVisibilityChange):
798         (BlackBerry::WebKit::InputHandler::notifyClientOfKeyboardVisibilityChange):
799         * WebKitSupport/InputHandler.h:
800         (InputHandler):
801         * WebKitSupport/SelectionHandler.cpp:
802         (BlackBerry::WebKit::SelectionHandler::setCaretPosition):
803         (BlackBerry::WebKit::SelectionHandler::updateOrHandleInputSelection):
804         * WebKitSupport/TouchEventHandler.cpp:
805         (BlackBerry::WebKit::TouchEventHandler::touchEventCancel):
806         (BlackBerry::WebKit::TouchEventHandler::handleTouchPoint):
807
808 2012-02-21  Ryosuke Niwa  <rniwa@webkit.org>
809
810         Remove the remaining uses of CSSStyleDeclaration in Editor
811         https://bugs.webkit.org/show_bug.cgi?id=78939
812
813         Reviewed by Enrica Casucci.
814
815         * WebCoreSupport/EditorClientBlackBerry.cpp:
816         (WebCore::EditorClientBlackBerry::shouldApplyStyle):
817         * WebCoreSupport/EditorClientBlackBerry.h:
818         (EditorClientBlackBerry):
819
820 2012-02-22  Mike Fenton  <mifenton@rim.com>
821
822         [BlackBerry] InputHandler has signed vs unsigned comparison.
823         https://bugs.webkit.org/show_bug.cgi?id=79261
824
825         Fix warning by casting the unsigned int to an int.
826
827         Reviewed by Rob Buis.
828
829         * WebKitSupport/InputHandler.cpp:
830         (BlackBerry::WebKit::InputHandler::rectForCaret):
831
832 2012-02-22  Ryosuke Niwa  <rniwa@webkit.org>
833
834         Remove the remaining uses of CSSStyleDeclaration in Editor
835         https://bugs.webkit.org/show_bug.cgi?id=78939
836
837         Reviewed by Enrica Casucci.
838
839         * WebCoreSupport/EditorClientBlackBerry.cpp:
840         (WebCore::EditorClientBlackBerry::shouldApplyStyle):
841         * WebCoreSupport/EditorClientBlackBerry.h:
842         (EditorClientBlackBerry):
843
844 2012-02-18  Antonio Gomes  <agomes@rim.com>
845
846         Fat fingers - cache the first rect-based hit test so we do not need to do it again
847         https://bugs.webkit.org/show_bug.cgi?id=79115
848
849         Reviewed by Adam Treat.
850
851         Our FatFingers implementation runs currently in two phases:
852         the first checks for the elements intrinsically clickable;
853         the second checks for elements made clickable by the page
854         (for example, a div with a onclick event listener attached to it).
855         For each phase, we perform a rect hittest, which is not needed since
856         the result of each is the same.
857
858         Patch introduces a caching mechanism so we avoid on rect hittest:
859         when the first phase runs, it caches each nodeset per document in
860         a hashmap. This second phase works with the cached results.
861
862         No behavioral change, but performance is better since we
863         avoid one (possibly expensive) rect hittest.
864
865         I measured the performance gain on https://www.kvd.se/, and we
866         save up to 0.04 seconds, by caching and re-using the results.
867
868         * WebKitSupport/FatFingers.cpp:
869         (BlackBerry::WebKit::dumpHitTestResult):
870         (BlackBerry::WebKit::FatFingers::findBestPoint):
871         (BlackBerry::WebKit::FatFingers::findIntersectingRegions):
872         (BlackBerry::WebKit::FatFingers::cachingStrategy):
873         (WebKit):
874         (BlackBerry::WebKit::FatFingers::getNodesFromRect):
875         * WebKitSupport/FatFingers.h:
876
877 2012-02-20  Antonio Gomes  <agomes@rim.com>
878
879         All default video/audio control elements should be rect-hit testable (Part II)
880         PR #139518 / MKS_3005538
881
882         Reviewed by George Staikos.
883
884         Add HTMLInputElement::isMediaControlElement as a criteria
885         to consider a element as clickable.
886
887         Note that is should be only used while in the "ClickableByDefault"
888         phase of FatFingers.
889
890         * WebKitSupport/FatFingers.cpp:
891         (BlackBerry::WebKit::FatFingers::isElementClickable):
892
893 2012-02-16  Antonio Gomes  <agomes@rim.com>
894
895         [BlackBerry] Implemented a way to defer client navigation change client notifications
896         https://bugs.webkit.org/show_bug.cgi?id=78848
897
898         Reviewed by Rob Buis.
899
900         Currently we postpone touch_down till touch_up if user touches
901         the screen and an input field has the WebKit focus. This is done
902         so we can scroll the page without hidding the vkb needlessly.
903
904         However, it breaks the conversion of touch to mouse events
905         if an input field has the focus in the following scenario:
906         an <input type=text> is focused and an user grab and-drag
907         a <input type=range> knob/slide. It does not work until the
908         user unfocuses the currently focused edit field.
909
910         Patch introduces a way to unfocus a currently focused input field,
911         without requesting the client to show or hide the virtual keyboard
912         right way. Instead it gets a delayed notification of the vkb mode requested
913         at either touch_released/mouse_up or touch_cancel time.
914
915         For now, due to content side issues with major web sites,
916         only delay navigation mode notification changes if we are not dealing with
917         input modes.
918
919         * WebKitSupport/InputHandler.cpp:
920         (BlackBerry::WebKit::InputHandler::InputHandler):
921         (BlackBerry::WebKit::InputHandler::nodeFocused):
922         (BlackBerry::WebKit::InputHandler::setElementFocused):
923         (BlackBerry::WebKit::InputHandler::setNavigationMode):
924         (WebKit):
925         (BlackBerry::WebKit::InputHandler::setDelayClientNotificationOfNavigationModeChange):
926         (BlackBerry::WebKit::InputHandler::processPendingClientNavigationModeChangeNotification):
927         (BlackBerry::WebKit::InputHandler::notifyClientOfNavigationModeChange):
928         (BlackBerry::WebKit::InputHandler::willOpenPopupForNode):
929         (BlackBerry::WebKit::InputHandler::setPopupListIndexes):
930         (BlackBerry::WebKit::InputHandler::spannableTextInRange):
931         (BlackBerry::WebKit::InputHandler::removeComposedText):
932         (BlackBerry::WebKit::InputHandler::firstSpanInString):
933         (BlackBerry::WebKit::InputHandler::setText):
934         (BlackBerry::WebKit::InputHandler::setRelativeCursorPosition):
935         * WebKitSupport/InputHandler.h:
936         (InputHandler):
937
938 2012-02-16  Antonio Gomes  <agomes@rim.com>
939
940         Crash @WebPagePrivate::enqueueRenderingOfClippedContentOfScrollableNodeAfterInRegionScrolling MKS_2986818
941         https://bugs.webkit.org/show_bug.cgi?id=78845
942
943         Reviewed by Rob Buis.
944
945         We were trying to operate on a cached Node when its page/frame/document
946         were gone to PageCache already. To avoid such problems, lets clean up
947         any document data we have cached when the Frame goes into the cache.
948
949         * WebCoreSupport/FrameLoaderClientBlackBerry.cpp:
950         (WebCore::FrameLoaderClientBlackBerry::didSaveToPageCache):
951         (WebCore):
952         * WebCoreSupport/FrameLoaderClientBlackBerry.h:
953         (FrameLoaderClientBlackBerry):
954
955 2012-02-16  Antonio Gomes  <agomes@rim.com>
956
957         [BlackBerry] Upstream touch handling related classes
958         https://bugs.webkit.org/show_bug.cgi?id=78509
959
960         Reviewed by Adam Treat and Rob Buis.
961
962         FatFingers is the class responsible to the whole touch
963         accuracy of the BlackBerry port. Initial upstream.
964
965         * WebKitSupport/FatFingers.cpp: Added.
966         (WebKit):
967         (BlackBerry::WebKit::FatFingers::fingerRectForPoint):
968         (BlackBerry::WebKit::hasMousePressListener):
969         (BlackBerry::WebKit::FatFingers::isElementClickable):
970         (BlackBerry::WebKit::isFieldWithText):
971         (BlackBerry::WebKit::distanceBetweenPoints):
972         (BlackBerry::WebKit::compareDistanceBetweenPoints):
973         (BlackBerry::WebKit::isValidFrameOwner):
974         (BlackBerry::WebKit::FatFingers::FatFingers):
975         (BlackBerry::WebKit::FatFingers::~FatFingers):
976         (BlackBerry::WebKit::FatFingers::findBestPoint):
977         (BlackBerry::WebKit::FatFingers::checkFingerIntersection):
978         (BlackBerry::WebKit::FatFingers::findIntersectingRegions):
979         (BlackBerry::WebKit::FatFingers::checkForClickableElement):
980         (BlackBerry::WebKit::FatFingers::checkForText):
981         (BlackBerry::WebKit::FatFingers::getPaddings):
982         (BlackBerry::WebKit::FatFingers::nodesFromRect):
983         (BlackBerry::WebKit::FatFingers::getRelevantInfoFromPoint):
984         (BlackBerry::WebKit::FatFingers::setSuccessfulFatFingersResult):
985         * WebKitSupport/FatFingers.h: Added.
986         (WebCore):
987         (WebKit):
988         (FatFingersResult):
989         (BlackBerry::WebKit::FatFingersResult::FatFingersResult):
990         (BlackBerry::WebKit::FatFingersResult::reset):
991         (BlackBerry::WebKit::FatFingersResult::originPosition):
992         (BlackBerry::WebKit::FatFingersResult::adjustedPosition):
993         (BlackBerry::WebKit::FatFingersResult::positionWasAdjusted):
994         (BlackBerry::WebKit::FatFingersResult::isTextInput):
995         (BlackBerry::WebKit::FatFingersResult::isValid):
996         (BlackBerry::WebKit::FatFingersResult::validNode):
997         (BlackBerry::WebKit::FatFingersResult::nodeAsElementIfApplicable):
998         (FatFingers):
999
1000 2012-02-16  Antonio Gomes  <agomes@rim.com>
1001
1002         [BlackBerry] Upstream touch handling related classes
1003         https://bugs.webkit.org/show_bug.cgi?id=78509
1004
1005         Reviewed by Adam Treat.
1006
1007         Initial upstream of the Blackberry specific single touch event
1008         handler class.
1009
1010         * blackberry/WebKitSupport/TouchEventHandler.cpp: Added.
1011         (WebKit):
1012         (BlackBerry::WebKit::hasMouseMoveListener):
1013         (BlackBerry::WebKit::hasTouchListener):
1014         (BlackBerry::WebKit::elementExpectsMouseEvents):
1015         (BlackBerry::WebKit::shouldConvertTouchToMouse):
1016         (BlackBerry::WebKit::TouchEventHandler::TouchEventHandler):
1017         (BlackBerry::WebKit::TouchEventHandler::~TouchEventHandler):
1018         (BlackBerry::WebKit::TouchEventHandler::shouldSuppressMouseDownOnTouchDown):
1019         [BlackBerry] Upstream touch handling related classes
1020         https://bugs.webkit.org/show_bug.cgi?id=78509
1021
1022         Reviewed by Rob Buis.
1023
1024         InRegionScrollableArea specializes the BlackBerry specific ScrollViewBase,
1025         working as a read-only wrapper object for a scrollable areas in the page.
1026         It is used in our client side to control in-region scrolling (scrollable boxes,
1027         inner frames, etc).
1028
1029         Initial upstream.
1030
1031         * WebKitSupport/InRegionScrollableArea.cpp: Added.
1032         (WebKit):
1033         (BlackBerry::WebKit::InRegionScrollableArea::InRegionScrollableArea):
1034         (BlackBerry::WebKit::InRegionScrollableArea::calculateMinimumScrollPosition):
1035         (BlackBerry::WebKit::InRegionScrollableArea::calculateMaximumScrollPosition):
1036         (BlackBerry::WebKit::InRegionScrollableArea::layer):
1037         (BlackBerry):
1038         * WebKitSupport/InRegionScrollableArea.h: Added.
1039         (WebCore):
1040         (WebKit):
1041         (InRegionScrollableArea):
1042
1043 2012-02-16  Antonio Gomes  <agomes@rim.com>
1044
1045         (BlackBerry::WebKit::TouchEventHandler::touchEventCancel):
1046         (BlackBerry::WebKit::TouchEventHandler::touchHoldEvent):
1047         (BlackBerry::WebKit::TouchEventHandler::handleTouchPoint):
1048         (BlackBerry::WebKit::TouchEventHandler::spellCheck):
1049         (BlackBerry::WebKit::TouchEventHandler::handleFatFingerPressed):
1050         (BlackBerry::WebKit::elementForTapHighlight):
1051         (BlackBerry::WebKit::TouchEventHandler::drawTapHighlight):
1052         * blackberry/WebKitSupport/TouchEventHandler.h: Added.
1053         (WebCore):
1054         (WebKit):
1055         (TouchEventHandler):
1056         (BlackBerry::WebKit::TouchEventHandler::lastFatFingersResult):
1057         (BlackBerry::WebKit::TouchEventHandler::resetLastFatFingersResult):
1058