mobile-safari

问题 I have a simple html page long enough that the user requires to scroll the page. I want at the bottom of the page to have a div with postion:fixed and inside him a textarea. When a user clicks on the text area and the virtual keyboard appears I want the div position to stay at bottom , not in the middle of the page like in this pic: Here is the code I've used: https://jsfiddle.net/capz19yg/ .inputFixed{ position:fixed; bottom:0px; right:0px; width:100%; height:50px; background-color:lightgrey

问题 My Angular application has a pdf download option. When i run my application in Iphone(IOS 12) Safari browser I get the following error message as shown in the image How can i resolve it? 回答1: If you are injecting an ancor tag into DOM programmatically as your solution, make sure you do not clear that up too soon. For me 100ms worked fine but since it's invisible either way I chose 1 second delay on clearing DOM up. Example code: this.fileApi.download(<your args>).subscribe((data: Blob) => {

问题 After onpopstate event triggered, window.alert, window.confirm etc not working. This is related console logs Image And this is what I tested. First I registered popstate event. And tried window.alert('abc'); // It works. Tried history.back() or click back button, then popstate event triggered. And tried window.alert('abc'); // Not working. I found the same issue, there is no answers left, so I post a question once again. Alert, confirm, and prompt not working after using History API on Safari

问题 Our requirement is to have our users login to an app via a URL and, having added the app to their homescreen as a PWA, maintain that logged-in status, so that a second login to the installed PWA is not required . This is certainly possible under Android/Chrome where the logged-in status can be initially stored and accessed by the PWA via a variety of mechanisms (including cookie, IndexedDB, cache). However, it now appears to us that a PWA under iOS 14/iPadOS 14 is tightly sandboxed and Safari

问题 Our requirement is to have our users login to an app via a URL and, having added the app to their homescreen as a PWA, maintain that logged-in status, so that a second login to the installed PWA is not required . This is certainly possible under Android/Chrome where the logged-in status can be initially stored and accessed by the PWA via a variety of mechanisms (including cookie, IndexedDB, cache). However, it now appears to us that a PWA under iOS 14/iPadOS 14 is tightly sandboxed and Safari

问题 Our requirement is to have our users login to an app via a URL and, having added the app to their homescreen as a PWA, maintain that logged-in status, so that a second login to the installed PWA is not required . This is certainly possible under Android/Chrome where the logged-in status can be initially stored and accessed by the PWA via a variety of mechanisms (including cookie, IndexedDB, cache). However, it now appears to us that a PWA under iOS 14/iPadOS 14 is tightly sandboxed and Safari

问题 Is there any workarounds that allows me to keep the "Prevent Cross Site Trackng" option enabled (as it is by default, so every user will have it on), and issue CORS cookies from my back-end api that is on a different domain than my angular app? My application flow is as follow: 1. User Logs in 2. The server authenticates, issues a JWT and stores the JWT inside of an HttpOnly cookie 3. All angular requests have the {withCredentials: true} This works perfectly fine on....windows desktop

问题 Is there any workarounds that allows me to keep the "Prevent Cross Site Trackng" option enabled (as it is by default, so every user will have it on), and issue CORS cookies from my back-end api that is on a different domain than my angular app? My application flow is as follow: 1. User Logs in 2. The server authenticates, issues a JWT and stores the JWT inside of an HttpOnly cookie 3. All angular requests have the {withCredentials: true} This works perfectly fine on....windows desktop

问题 I have added Firebase Dynamic Link in my app, when I open in iPhone link through Google Chrome , it redirects me to the app, but when I'm trying to open app through Safari (I'm opening links through the Notes, not directly from the Safari), it doesn't open the app. I'm testing on real device, not in simulator. I have followed official Firebase Dynamic Links Tutorial. What can be wrong and how is possible to fix that? 回答1: My problem was that in Xcode in Capabilities Tab in Associated Domains,

问题 I would like to disable the swipe back animation totally on a SPA. That would allow me to use some swiping gestures within the SPA. At the moment on iOS you tend to also trigger the swipe back gesture when triggering certain gestures. I have found this previous post about how to disable it: iOS 7 - is there a way to disable the swipe back and forward functionality in Safari? They suggest following: 1) CSS only fix for Chrome/Firefox html, body { overscroll-behavior-x: none; } 2) JavaScript