|
|
Quellcode |
1 2 3 4 5 6 7 8 9 10 11 12 |
var iHeight = window.innerHeight;
function resize() {
if(window.innerHeight != iHeight) {
iHeight = window.innerHeight;
document.body.style.height = iHeight + 'px';
}
}
var timeOut = null;
window.onresize = function() {
if(timeOut) clearTimeout(timeOut);
timeOut = setTimeout(resize, 100);
}
|
Dieser Beitrag wurde bereits 6 mal editiert, zuletzt von »indexofrefraction« (4. April 2019, 07:40)
You mean resizing to the currently visible space - technically it might be possible, but more tricky and complicated and far less optimal. That would require an additional layer with a fake-size to trick Safari into allowing the scrolling. And then during dragging probably resizes would be necessary to adopt size because the 'remaining-bars-down-height' is not really fix defined and could be anything. And constant resizing during dragging would be bad for performance and might result in a jerky controlling. And then the question about the pano control itself during that phase? Should it be disabled? Should it pan the pano and scroll the page at the same time...?Wouldn't it be possible to show the bottom bar even before going fullscreen?
. No problem, the need for swipe-up gestures to get fullscreen mode will be detected anytime in any situation. That means you can anytime have the bars there or bring them there and there is then there is a possibility and information to swipe them away.What if the page is loaded with the iPhone already in landscape mode?
Sorry, I don't understand...?After switching to landscape mode, how could the user know how to restore the view of the button bar at the bottom (and to go fullscreen)? Will a hint be shown similarly to the arrow and the "swipe up" text in your video?
As soon as possible, I can't wait tooLast question: when will 1.20 be released? I can't wait![]()
.