Changeset 138804 in webkit
- Timestamp:
- Jan 4, 2013 9:16:08 AM (11 years ago)
- Location:
- trunk/Source
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/Source/WebCore/ChangeLog
r138802 r138804 1 2013-01-04 Anthony Scian <ascian@rim.com> 2 3 [Blackberry] Static code analysis warning fixes 4 https://bugs.webkit.org/show_bug.cgi?id=105679 5 6 Reviewed by Rob Buis. 7 8 klocwork 1855: fixed by caching page, check against NULL and use cached value 9 10 * platform/blackberry/RenderThemeBlackBerry.cpp: 11 (WebCore::determineFullScreenMultiplier): 12 1 13 2013-01-04 Hans Muller <hmuller@adobe.com> 2 14 -
trunk/Source/WebCore/platform/blackberry/RenderThemeBlackBerry.cpp
r138712 r138804 168 168 #if ENABLE(FULLSCREEN_API) && ENABLE(VIDEO) 169 169 if (element && element->document()->webkitIsFullScreen() && element->document()->webkitCurrentFullScreenElement() == toParentMediaElement(element)) { 170 if (element->document()->page()->deviceScaleFactor() < scaleFactorThreshold) 171 fullScreenMultiplier = fullScreenEnlargementFactor; 172 173 // The way the BlackBerry port implements the FULLSCREEN_API for media elements 174 // might result in the controls being oversized, proportionally to the current page 175 // scale. That happens because the fullscreen element gets sized to be as big as the 176 // viewport size, and the viewport size might get outstretched to fit to the screen dimensions. 177 // To fix that, lets strips out the Page scale factor from the media controls multiplier. 178 float scaleFactor = element->document()->view()->hostWindow()->platformPageClient()->currentZoomFactor(); 179 float scaleFactorFudge = 1 / element->document()->page()->deviceScaleFactor(); 180 fullScreenMultiplier /= scaleFactor * scaleFactorFudge; 170 if (Page* page = element->document()->page()) { 171 if (page->deviceScaleFactor() < scaleFactorThreshold) 172 fullScreenMultiplier = fullScreenEnlargementFactor; 173 174 // The way the BlackBerry port implements the FULLSCREEN_API for media elements 175 // might result in the controls being oversized, proportionally to the current page 176 // scale. That happens because the fullscreen element gets sized to be as big as the 177 // viewport size, and the viewport size might get outstretched to fit to the screen dimensions. 178 // To fix that, lets strips out the Page scale factor from the media controls multiplier. 179 float scaleFactor = element->document()->view()->hostWindow()->platformPageClient()->currentZoomFactor(); 180 float scaleFactorFudge = 1 / page->deviceScaleFactor(); 181 fullScreenMultiplier /= scaleFactor * scaleFactorFudge; 182 } 181 183 } 182 184 #endif -
trunk/Source/WebKit/blackberry/Api/InRegionScroller.cpp
r138478 r138804 260 260 InRegionScrollableArea* curr = static_cast<InRegionScrollableArea*>(*rit); 261 261 RenderLayer* layer = curr->layer(); 262 263 if (layer && layer->renderer()->isRenderView()) { // #document case 262 if (!layer) 263 continue; 264 265 if (layer->renderer()->isRenderView()) { // #document case 264 266 FrameView* view = toRenderView(layer->renderer())->frameView(); 265 267 ASSERT(view); -
trunk/Source/WebKit/blackberry/ChangeLog
r138699 r138804 1 2013-01-04 Anthony Scian <ascian@rim.com> 2 3 [Blackberry] Static code analysis warning fixes 4 https://bugs.webkit.org/show_bug.cgi?id=105679 5 6 Reviewed by Rob Buis. 7 8 Klocwork issue 959: check layer against NULL since it is used in both cases 9 of the subsequent if-stmt 10 11 * Api/InRegionScroller.cpp: 12 (BlackBerry::WebKit::InRegionScrollerPrivate::calculateInRegionScrollableAreasForPoint): 13 1 14 2013-01-02 Jacky Jiang <zhajiang@rim.com> 2 15
Note: See TracChangeset
for help on using the changeset viewer.