Definitions
for a further explanation of these terms.
CSS pixelsExpand and c it’s this pixels that are taken as measurement grid for all CSS declarations.
Device pixelsFormal number of pixels on device. Generally useless to web developers.
Device pixel ratioThe ratio of physical pixel count and ideal viewport. In the iPhone 4G example the device pixel ratio would be 640 / 320 = 2.
blog post for more information, though these posts use an older definition
Layout viewportThe initial area of the HTML element. CSS declarations such as width: 20% are calculated relative to this viewport. Is usually quite a bit wider than the visual viewport.
Visual viewportThe actual screen viewport through which you look at the layout viewport.
Ideal viewportThe one you get when using width=device-width. See
for more information.
Viewport properties
This table looks into the properties that are necessary to read out useful information about the three viewports and the two types of pixels.
screen.width and screen.height
Dimensions of the ideal viewport.
Both avail
screen.width should return the dimensions of the ideal viewport. The older implementation returns the number of physical device pixels, but that’s now seen as wrong.
PhysicalGives the physical screen dimensions.
PortraitAlways gives the portrait values even when in landscape.
LayoutGives the layout viewport dimensions.
AvailGives the available screen height (minus toolbars and such) instead of the actual height.
BothDevice pixel ratio is 1, so the ideal viewport has the same dimensions as the screen and I can’t figure out which one the properties return.
p + pPhysical and portrait
The HTC Android 4 always gives portrait values. The other six get it right.
Opera 16 on Nexus gives the available ideal viewport. The one on Sony does it right.
MeeGo increases DPR from 1 to 1.5 when you use width=device-width.
UC Mini gives 800x600, which makes no sense whatsoever.
UC 8 is crazy. It should be sent to a sanatorium.
window.innerWidth and window.innerHeight
Dimensions of the visual viewport in CSS pixels.
LayoutGives the layout viewport dimensions.
Opera Mini: always equal to documentElement.client, which contains weird values.
I cannot zoom Nokia Xpress and thus cannot test if it supports it correctly. My guess is No, though.
UC Mini gives , which makes no sense whatsoever. Also, I cannot zoom.
UC 8 is crazy. It should be sent to a sanatorium.
documentElement. clientWidth and documentElement. clientHeight
Dimensions of the layout viewport in CSS pixels.
I don’t understand Opera Mini. Sometimes it gives the layout viewport in one orientation and retains those values for the other one, but sometimes it does something else.
UC 8 is crazy. It should be sent to a sanatorium.
Puffin’s height in landscape mode is wrong.
devicePixelRatio
device pixels divided by dips
Opera Mini and Puffin and Dolfin return 1 while they shouldn’t.
MeeGo increases DPR from 1 to 1.5 when you use width=device-width.
UC 8 is crazy. It should be sent to a sanatorium.
Nintendo returns 2, while it should be 1.49something.
One’s DPR is correct for portrait, but not for landscape.
FF OS gives 1.6875 while it should be 1.5.
Tested browsers
1.2.1; November 2013
WebKit 536
Default browser on iPhone 4S with iOS 6.1.3
WebKit 537
Default browser on iPad 2 with iOS 7.0.3
WebKit 533
Default browser on HTC Legend, Android 2.2
Default browser on LG Optimus something, Android 2.2
Default browser on Samsung Galaxy Pocket, Android 2.3.6
WebKit 534
Default browser on Samsung Galaxy Note I, Android 4.0.3
Default browser on Sony Xperia S, Android 4.1.2
Default browser on LG L5, Android 4.1.2
Default browser on Xiaomi M2, Android 4.1.1
Default browser on Huawei C8813, Android 4.1.1
Default browser on Samsung Galaxy S3, Android 4.1.2
Default browser on HTC One X, Android 4.2.2
WebKit 535
Default browser on Samsung Galaxy S4, Android 4.2.2
On Sony Xperia S, Android 4.1.2. This is a downloaded version from Google
It will be interesting to see if Samsung’s purported Chrome 18 is really the real Chrome 18.
Blink (Chromium 30)
On HTC One X, Android 4.2.2
On Nexus 7, Android 4.3
Opera Mini
Proxy browser
7.0.5 on iPad 2, iOS 7.0.3
7.1 on BlackBerry 9800 (OS6)
7.1 on Nokia PureView 808, Symbian Belle
7.5 on Samsung Galaxy Note I, Android 4.0.3
Opera Mobile 12
12.00 on Nokia E7, Symbian Anna
12.10 on Samsung Galaxy Pocket, Android 2.3.6
Opera Mobile 16
Blink (Chromium 29)
On Sony Xperia S, Android 4.1.2
On Nexus 7, Android 4.3
BlackBerry 6
WebKit 534
Default browser on BB Torch 9800 (OS6)
BlackBerry 7
WebKit 534
Default browser on BB Torch 9810 (OS7)
BlackBerry PB
WebKit 536
Default browser on PlayBook with OS 2.1.0
BlackBerry 10
WebKit 537
Default browser on BlackBerry Z10 (BB OS 10.1)
This device has 1GB of internal memory instead of the customary 2GB, which may matter in performance tests.
Gecko ; this version was used for some Firefoxes from 3 to 4.
Proxy browser
3.7 on the Nokia Asha 311, S40.
This browser used to be called Ovi. Nokia developed it because it saw how succesful Opera was on Nokia’s own devices.
WebKit 534
Default browser on Nokia N950, MeeGo Harmattan 1.2
Originally slated as Symbian’s successor, MeeGo was ousted in favour of Windows Phone. Some devices were sold, however, and a Finnish company is trying to re-start MeeGo under the name Sailfish. Also, rumour has it that Nokia is quietly hiring back ex-MeeGo people, so a Nokia-based restart is not entirely impossible.
WebKit 533
Default browser (7.3) on Nokia E7, Symbian Anna
The next-to-last Symbian build. I don’t think it was the prime Sy it was replaced by Belle fairly soon. But it’ll be in some people’s pockets.
WebKit 535
Default browser (8.3) on Nokia PureView 808, Symbian Belle FP2
The most recent Symbian build.
Doesn’t mention a rendering engine
Proxy browser
8.8 on HTC One X, Android 4.2.2
WebKit 534
UC 8.5.1 on Xiaomi M2 (Android 4.1.1)
UC 9.2.3 on Huawei C8813 (Android 4.1.1)
The largest Chinese browser. This is the full variant, not the proxy. These browsers were pre-installed (next to Android WebK don’t ask me why).
WebKit 534
2.1 Free Edition on Samsung Galaxy S4, Android 4.2.2
Claims to be Chrome 11
WebKit 536
Nintendo browser 2.0.0 on Wii U 4.0.0
Supposed to be based on NetFront.
WebKit 534
Beta 1.3.1 on Sony Xperia S, Android 4.1.2.
Independent full browser for Android. The non-beta is a skin over the Android default browser. The beta uses their own WebKit port.
WebKit 533
4.2.2 on HTC One X, Android 4.2.2
This is the downloadable, international browser TenCent created.
WebKit 537
Default browser on Ref.Device-PQ by S Tizen 2.2
Tizen is an OS jointly being developed by Samsung and Intel. I expect Samsung to start producing devices this year, and it will get a few percent of market share.
Default browser on Nokia Lumia 800, Windows Phone 7.5.
Default browser on Nokia Lumia 820, Windows Phone 8.0.
Firefox OS
Geekphone/Telef&nica (Peak and/or qcom); Boot2Gecko 1.0.1.0-prerelease
Firefox Android
25 on HTC One X, Android 4.2.2
Browsers by WebKit version:
Android 3 and 4
BB 6 and 7
BlackBerry PlayBook
BlackBerry 10
Mouse/touch coordinates
These tests were last updated on 19 March 2013.
In CSS pixels, relative to the visual viewport
clientX/Y = pageX/Y - window.pageX/YOffset
pageEqual to pageX/Y
I don’t understand IE10’s values, but they’re wrong.
In CSS pixels, relative to the layout viewport
pageX/Y uses the same coordinate system as position: absolute. This is usually what you want.
In device pixels, relative to the visual viewport
screenX/Y = clientX/Y * devicePixelRatio * zoom
zoom = documentElement.clientWidth / window.innerWidth
clientEqual to clientX/Y
pageEqual to pageX/Y
I’m not sure what Safari is doing, but it’s wrong.
BB7 and PB add something to the clientY values to arrive at screenY.
I don’t understand the Xpress and MeeGo values.
Tizen uses pageX/Y, but adds something to the Y.
I don’t know what IE is doing, but it’s wrong.
Meta viewport
Below you find a series of tests aimed at changing the width of the meta viewport after page load.
There’s also the
for the meta viewport, which gives a lot more details.
Sets the dimensions of the layout viewport.
&meta name="viewport" content="width = 380"&
&meta name="viewport" content="width = device-width"&
Should narrow the layout viewport to the indicated width. The device-width
should equal screen.width.
Chrome changes the size of the layout viewport, but does not zoom the page in or out.
Opera Mini supports the meta viewport. but chooses different values than other browsers on the same device.
Xpress uses a default width of 240px in my test, and doesn’t really change that with a meta viewport, although it sometimes extends the canvas. Assume it’s not supported.
Change immediately
Change the tag directly after it’s been written into the page
&meta id="testViewport" name="viewport" content="width = 380"&
var mvp = document.getElementById('testViewport');
mvp.setAttribute('content','width=480');
See above for Chrome.
Change later
Change the tag once the page has been loaded
&meta id="testViewport" name="viewport" content="width = 380"&
window.onload = function () {
var mvp = document.getElementById('testViewport');
mvp.setAttribute('content','width=580');
See above for Chrome.
Remove the tag entirely
&meta id="testViewport" name="viewport" content="width = 380"&
window.onload = function () {
var mvp = document.getElementById('testViewport');
mvp.removeAttribute('content');
I expect the page becomes as wide as the def i.e. behaves the same as if no meta viewport were set.
Supported from Android 4 on.
Tested browsers
1.0.5; March 2013
WebKit 534
Default browser on iPad 2 with iOS 5.1.1
WebKit 536
Default browser on iPhone 4S with iOS 6.1.1
WebKit 533
Default browser on HTC Legend, Android 2.2
Default browser on LG Optimus something, Android 2.2
Default browser on Sony Xperia S, Android 2.3.7
WebKit 534
Default browser on Packard Bell tablet, Android 3.2.1
WebKit 534
Default browser on HTC One X, Android 4.1.1
Default browser on Samsung Galaxy Note I, Android 4.0.3
WebKit 535
On Nexus 7, Android 4.2.1
WebKit 537
On Samsung Galaxy Note I, Android 4.0.3
Opera Mini
Proxy browser
7.5 on Samsung Galaxy Note I, Android 4.0.3
7.1 on BlackBerry 9800 (OS6)
7.1 on Nokia E71 (SymbianOS/9.2)
7.0.5 on iPad 2, iOS 5.1.1
Opera Mobile 12
12.10 on HTC One X, Android 4.1.1
12.00 on Nokia E7, Symbian Anna
Opera Mobile 14
WebKit 537
14.0 on Sony Xperia S, Android 2.3.7
BlackBerry 6
WebKit 534
Default browser on BB Torch 9800 (OS6)
BlackBerry 7
WebKit 534
Default browser on BB Torch 9810 (OS7)
BlackBerry PB
WebKit 536
Default browser on PlayBook with OS 2.1.0
BlackBerry 10
WebKit 537
Default browser on BlackBerry Z10 (BB10). This device has 1GB of internal memory instead of the customary 2GB, which may matter in performance tests.
Proxy browser
2.3 on the Nokia Asha 311, S40.
This browser used to be called Ovi. Nokia developed it because it saw how succesful Opera was on Nokia’s own devices.
WebKit 534
Default browser on Nokia N950, MeeGo Harmattan 1.2
Originally slated as Symbian’s successor, MeeGo was ousted in favour of Windows Phone. Some devices were sold, however, and a Finnish company is trying to re-start MeeGo under the name Sailfish. And who knows? Ex-Nokia people have good operator contacts.
WebKit 533
Default browser on Nokia E7, Symbian Anna
The next-to-last Symbian build. I don’t think it was the prime Sy it was replaced by Belle fairly soon. But it’ll be in some people’s pockets.
WebKit 535
Default browser on Nokia PureView 808, Symbian Belle SP2
The most recent Symbian build.
WebKit 533
UC 8.6.1 on Packard Bell tablet, Android 3.2.1.
The largest Chinese browser. I’m testing the full variant, not the proxy.
WebKit 534
Default browser on Nintendo Wii U
NetFront, by the Japanese Access company, used to be big on proprietary Samsung and Sony Ericsson systems. It is now switching to WebKit from their own rendering engine, and to the gaming device and TV markets.
WebKit 534
Beta 1.3.1 on Samsung Galaxy Note I, Android 4.0.3.
Independent full browser for Android. The non-beta is a skin over the Android default browser. The beta uses their own WebKit port.
WebKit 534
3.5.2 on HTC One X, Android 4.1.1
Formerly QQ browser by the Chinese company TenCent. Domestic competitor of UC.
WebKit 537
Default browser on Lunchbox prototype by Intel, Tizen 2.0.0a3
Tizen is an OS jointly being developed by Samsung and Intel. I expect Samsung to start producing devices this year, and it will get a few percent of market share.
Default browser on Nokia Lumia 800, Windows Phone 7.
Default browser on Nokia Lumia 820, Windows Phone 8.
19 on HTC One X, Android 4.1.1
General note on One and UC: the browsers I test are not particularly representative for the actual browsers that are used in the wild. Though some may be default browsers on Asian Android devices, most of them get their market share from being pre-installed on feature phones or game consoles.I’m working on getting more representative test devices.
Browsers by WebKit version:
Android 3 and 4
BB 6 and 7
BlackBerry PlayBook
Opera Mobile 14
BlackBerry 10三星nore3 n9002联通版 怎么设置手机皮套窗口的自动关屏时间，说的在通俗点就是盖子合上，_百度知道
三星nore3 n9002联通版 怎么设置手机皮套窗口的自动关屏时间，说的在通俗点就是盖子合上，
三星智能皮套在手机中设置路径：设定-我的设备/一般-配件-查找“智能保护套”字样（提示：需要安装皮套后才会显示），然后根据选项进行设置即可。1.自动解锁：安全锁禁用时翻开封面以解锁屏幕。2.视窗窗口色彩。3.选择信息显示封面：在视窗上显示天气信息、健走伙伴
其他类似问题
为您推荐：
提问者采纳
显示设置里面就有
不然就是 安全里面可以设置
没有，只有主屏幕的时间和按钮的时间
那就没办法了
估计是漏洞
去售后吧宝贝
你手机是不是三星只要系统一样你可以详细的说下啊 比如设置～设备～显示……
看过了 点击显示 里面有休眠
就可以设置了
提问者评价
太给力了，你的回答完美解决了我的问题！
手机皮套的相关知识
等待您来回答
下载知道APP
随时随地咨询
出门在外也不愁三星Nor flash芯片识别_百度文库
两大类热门资源免费畅读
续费一年阅读会员，立省24元！
评价文档：
三星Nor flash芯片识别
上传于||文档简介
&&根​据​芯​片​型​号​查​看​N​o​r​ ​f​l​a​s​h​信​息
大小：2.42MB
登录百度文库，专享文档复制特权，财富值每天免费拿！
你可能喜欢后使用快捷导航没有帐号？
只需一步，快速开始
& & & & 三星 i9300（Galaxy S III）论坛讨论区
1 / 127 页
1 / 127 页
Powered by}