chrome-ios

Chrome on iPhone overflows content on empty page (on new tab only, not reload)

由 只愿长相守 提交于 2021-01-04 03:15:16
问题 On IOS Chrome, the body overflows on a new tab or page with no content, but if the page is reloaded, the problem is fixed. It poses a problem for any element positioned at the bottom (absolute or fixed). Here is the code to reproduce the problem: <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width,minimum-scale=1, maximum-scale=2, initial-scale=1"> <meta name="apple-mobile-web-app-capable" content="yes"> <style>* { box-sizing:

Chrome on iPhone overflows content on empty page (on new tab only, not reload)

由 女生的网名这么多〃 提交于 2021-01-04 03:12:49
问题 On IOS Chrome, the body overflows on a new tab or page with no content, but if the page is reloaded, the problem is fixed. It poses a problem for any element positioned at the bottom (absolute or fixed). Here is the code to reproduce the problem: <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width,minimum-scale=1, maximum-scale=2, initial-scale=1"> <meta name="apple-mobile-web-app-capable" content="yes"> <style>* { box-sizing:

Chrome on iPhone overflows content on empty page (on new tab only, not reload)

由 百般思念 提交于 2021-01-04 03:11:47
问题 On IOS Chrome, the body overflows on a new tab or page with no content, but if the page is reloaded, the problem is fixed. It poses a problem for any element positioned at the bottom (absolute or fixed). Here is the code to reproduce the problem: <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width,minimum-scale=1, maximum-scale=2, initial-scale=1"> <meta name="apple-mobile-web-app-capable" content="yes"> <style>* { box-sizing:

Chrome on iPhone overflows content on empty page (on new tab only, not reload)

由 僤鯓⒐⒋嵵緔 提交于 2021-01-04 03:11:01
问题 On IOS Chrome, the body overflows on a new tab or page with no content, but if the page is reloaded, the problem is fixed. It poses a problem for any element positioned at the bottom (absolute or fixed). Here is the code to reproduce the problem: <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width,minimum-scale=1, maximum-scale=2, initial-scale=1"> <meta name="apple-mobile-web-app-capable" content="yes"> <style>* { box-sizing:

Intercepting AJAX requests on Chrome for iOS?

由 喜夏-厌秋 提交于 2020-01-02 07:30:22
问题 I intercept AJAX requests in my site by altering the XMLHttpRequest.prototype open and send methods. This method worked without any troubles in all the browsers I tested. However, when it comes to Chrome for iOS (iPhone) the code has the weirdest bug: it's like it continuously fire the code I changed in the prototype (ending up crashing, obviously). Here's a super-minimal example of what I am doing: var open = XMLHttpRequest.prototype.open; // Caching the original XMLHttpRequest.prototype

Disable Chrome's pull-to-refresh on iPhone

由 ♀尐吖头ヾ 提交于 2019-12-18 03:34:28
问题 I am implementing a drawing app on my site and trying to prevent overscroll while the user draws on the canvas. Despite trying several reported solutions, I cannot disable Chrome's pull-to-refresh. According to https://developers.google.com/web/updates/2017/11/overscroll-behavior, the following one line of css should do the trick..yet pull-to-refresh and an annoying user experience persists. Any ideas? <!DOCTYPE html> <html> <style type="text/css"> body { /* Disables pull-to-refresh but

How do you go to the previous route in iron-router?

由 家住魔仙堡 提交于 2019-12-12 10:57:13
问题 I'm using an event handler to go to the previous URL/route: 'click #back': -> history.back() This works in Chrome desktop, Chrome devtools mobile device view, and in Safari on a physical device itself (iOS 8.1.2), but not in Chrome on the device. Behavior is: Load / Click link to /foo URL changes to /foo, and foo template renders Click #back URL changes to / briefly, then changes back to /foo. The page body does not change. (Correct behavior is the URL permanently changes to /, and the /

Do all browsers on iOS use WKWebview or UIWebVIew?

由 喜夏-厌秋 提交于 2019-12-07 04:46:45
问题 I am curious about third part browser on iOS（Chrome or FireFox） Does all of them use the WkWebview or UIWebVIew to show then web page, but do many extra work like cache etc? So, if I want to write a browser on iOS, I must use WkWebview to show the web page and wrapping it to do more stuff？ 回答1: Yes, Apple forbids other web engines explicitly (or only allows the WebKit respectively) in § 2.5.6 of App Store Review Guidelines: 2.5.6 Apps that browse the web must use the appropriate WebKit

Intercepting AJAX requests on Chrome for iOS?

由 放肆的年华 提交于 2019-12-06 00:27:55
I intercept AJAX requests in my site by altering the XMLHttpRequest.prototype open and send methods. This method worked without any troubles in all the browsers I tested. However, when it comes to Chrome for iOS (iPhone) the code has the weirdest bug: it's like it continuously fire the code I changed in the prototype (ending up crashing, obviously). Here's a super-minimal example of what I am doing: var open = XMLHttpRequest.prototype.open; // Caching the original XMLHttpRequest.prototype.open = function(method, url, async, user, pass) { alert('open'); // Here is my code open.call(this, method

window.opener not set in iOS Chrome

由 孤街醉人 提交于 2019-12-05 23:11:41
问题 In one file, I have <a href="t2.html" target="_blank">go</a> In t2.html I have <script> document.write(window.opener); </script> On Safari on iOS, and on Chrome on the Mac and on pretty much every other browser, it prints out [object Window] like you'd expect. On Chrome on iOS, I get null . How do I get to the window that opened this window? 回答1: This seems to be a bigger story. See Bugtracker here: http://code.google.com/p/chromium/issues/detail?id=136610&q=window.opener&colspec=ID%20Pri
订阅 chrome-ios