Changeset 139629 in webkit
- Timestamp:
- Jan 14, 2013 11:09:44 AM (11 years ago)
- Location:
- trunk/Source/WebKit/blackberry
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/Source/WebKit/blackberry/Api/WebPage.cpp
r139582 r139629 1700 1700 bool WebPagePrivate::respectViewport() const 1701 1701 { 1702 return m_forceRespectViewportArguments || contentsSize().width() <= m_virtualViewportSize.width() ;1702 return m_forceRespectViewportArguments || contentsSize().width() <= m_virtualViewportSize.width() + 1; 1703 1703 } 1704 1704 -
trunk/Source/WebKit/blackberry/ChangeLog
r139582 r139629 1 2013-01-14 Jacky Jiang <zhajiang@rim.com> 2 3 [BlackBerry] Zoom is still possible when user-scalable=no 4 https://bugs.webkit.org/show_bug.cgi?id=106809 5 6 Reviewed by George Staikos. 7 8 PR: 274566 9 On wordpress.com, the contents were rendered at the width 343 which was 10 1 css pixel larger than the expected device-width 342 so that we didn't 11 respect the viewport. 12 There was a RenderBlock on the page which contained "\n" and an 13 inline-block. "\n" took 0.78 width and the inline-block took 342 width 14 and they were unfortunately placed in the same InlineBox which caused 15 the contents width 1 css pixels larger than the device-width. 16 Allow the contents width to be 1 css pixel larger and still respect the 17 viewport in such a special case. 18 19 * Api/WebPage.cpp: 20 (BlackBerry::WebKit::WebPagePrivate::respectViewport): 21 1 22 2013-01-13 Xiaobo Wang <xbwang@torchmobile.com.cn> 2 23
Note: See TracChangeset
for help on using the changeset viewer.