I have an HTML animation created using Adobe Edge Animate that plays fine in my desktop browser version of Safari (9.0.1)
It doesn't work on the iPad platform it is targeted at, and it transpires that some of the image names in the assets folder are not capitalised. The HTML is calling for 'pasted.svg' for example and the file is called 'Pasted.svg'
OS Safari seems to be using some kind of fuzzy logic to be kind to the developer and is working out which image to use. iOS is not, which doesnt help me bugtest.
Is there a way I can duplicate this behaviour on OS Safari so I dont need to keep loading up to the iPad to test if the animations will work?
Thanks
Related
I started porting my iOS app (which works on iPhone and iPad) over to Mac via the Catalyst route but WKWebView is behaving very strange. All the content is too small, it looks like it thinks the monitor is 2 times bigger.
The website I am displaying is responsive and works correctly on iOS devices as well as a Mac in Safari. On iOS it looks the same in Safari and WKWebView but with Catalyst and Mac Safari, the Catalyst version is much smaller.
I also tried this with Google.com and the issue is the same.
Anyone knows what might be happening? Since this doesnt happen just to the single site, I guess the issue is with WKWebView?
Are you using the Mac or iPad idiom for your Catalyst app? The “iPad” idiom, which is the default (and only option for apps that support Catalina), will downscale your entire app to 77% it’s original size. Read more here: https://developer.apple.com/documentation/uikit/mac_catalyst/choosing_a_user_interface_idiom_for_your_mac_app
My guess is that your app is being downscaled, including the web content. You could fix that by switching to the Mac idiom. If that’s not an option for whatever reason, maybe you could try scaling the web content back up with CSS?
Im creating an web application in Angular 5 that should work fine also on mobile devices. The progress bar of it is an svg image, created in Adobe Illustrator and exported to svg. I have made it work fine on Android, Mac and Windows (all browsers) but Im having a problem with clip-path being rendered on Chrome or Safari browser that runs on IPhone IOS.
I have tried managing it by normal
clip-path: url(#clip-path);
and also by webkit specific:
-webkit-clip-path: url(#clip-path);
But insted of something like that:
Image preview:
I get this on Safari or Chrome on IOS:
Wrong image preview:
So it looks like clipping is completely ignored, but weird thing is that on Mac it works fine.
Please suggest how to solve it, as Im struggling with it for few days.
I have also created demo on
Stackblitz
I have an app that is built with PhoneGap. One page in the app copies the contents of other page's canvases as images. This worked fine on older versions of iOS, but recently I noticed that the copied canvases are sometime blank. The rest of the page is rendered correctly. I don't know which iOS version it crept in, but I'm currently running iOS 10.3.1 on my iPad Pro. This does not happen when the same code is running as a WebApp in mobile Safari (or Chrome, or on my Mac laptop browsers).
Using the debugger on the App, I can restore the page by simply toggling the display property. This indicates to me that it's a rendering bug in the built-in Webview that Cordova uses. I currently have a patch that toggles the display property. This works, but it causes flickering even with requestAnimationFrame() or SetTimeout(fn, 0).
The app is built with cli-6.5.0 using PhoneGap Build.
Has anyone else seen this bug or have a better patch?
Follow up:
Toggling visibility fixes the flickering. When the problem occurs the canvas behaves like it's not visible, but the DOM reports that it is. Also the problem seems to occur when the canvas is copied under an Ajax callback. Delaying the processing with setTimeout() does not solve the problem.
How can I specify the icon/ image thumbnail and text used in the iOS Chrome new tab? It doesn't appear to be http://example.com/favicon.ico.
Screenshot of iOS Chrome new tab
Quick and easy solution
Apparently you have only one icon, favicon.ico, which is mostly ignored by mobile browsers. You should at least define a Touch icon. You can use a service such as Real Favicon Generator to create everything and support all browsers.
Full disclosure: I'm the author of this site.
Precise (but probably too elaborate) solution
Run the compatibility test to understand which icon is actually displayed by Chrome in this particular place. For example, if you discover that Chrome takes the 152x152 Apple Touch icon, well, now you know what you need.
Problem: you probably want to support all scenarios (Android Chrome, iOS Safari, etc.), not only the "New tab" of iOS Chrome. So even if you find out, you will probably want to declare other icons.
I have searched around on here, but couldn't find anything to answer my question. I have developed a custom app for the iPad; it involves using a set of PDf documents that change pages based on a 1 second time frame. To achieve this is have used the 'PDF Reader Core for iOS' external library. Please find the link here: https://github.com/vfr/Reader
The app works perfectly fine on the actual iPad, however I also wish to run the app on Mac Mini Machines, so the obvious thought I had was to boot the project in the iOS Simulator on the machines (saves me recoding it for OSX.). Now, here is my issue. The app works pretty smoothly in the simulator, the only issue I have is that there is a slight render lag between the page change on the Simulator. It isn't at full resolution, and appears blur whilst it renders, however the time frame to change is so quick that the simulator doesn't have enough time to render to full resolution. I have also emailed the developer of the library and he provided some suggestions however, these didn't seem to fix the issue.
I am aware that this could be to do with the actual PDF Reader itself, however I wanted to ask if anyone had any suggestions if this could be fixed in regards to the iOS Simulator? Any way to speed up the simulator?
I am using OSX Yosemite, Xcode 6.4 and Objective-C.
It seems at this moment i may have to recode for OSX. Any suggestions would be highly appreciated.
Thanks