I have the problem that sometimes in UIWebView a page is not fully loaded.
There is a picture gallery and if page is not fully loaded (means I don't get the delegate "ViewDidFinishLoading") some pictures are not loaded.
The picture gallery uses jquery.
As I mentioned it's not every time.
Are you looking to see if didFailLoadWithError: is getting called in this situation?
And if so, then find out why.
Related
I have a site that is using fontawesome. I am lazy loading many of the CSS files to increase first page load time, etc.
However, I need the fa-phone-alt to working on first load because it appears at the top of the page.
Can anyone provide guidance as to how I an add inline style just for the fa-phone-alt so that it works without having to load the entire style sheet?
Hope I am explaining this well enough.
Thanks.
I'm not sure how to solve exactly what you're asking, but a workaround could be that you download an SVG of a phone and place it so it loads instantly.
I have a problem with using Bootstrap plus Masonry for my layout. Trying it out on my computer, it works perfectly, but when I upload it to GitHub pages or Godaddy hosting, it sometimes gets destroyed like the image I shared. I bought Lightgallery and tried it instead of Fancybox to make the photo gallery, just in case something there was making a problem, but it's the same.
The problem being Masonry or bootstrap, I can't get rid of bootstrap but could use an alternative to Masonry. My client just needs the Pinterest-like layout.
It's very frustrating because it works perfectly until it is live. I tried a lot of things but nothing has worked. Thank you for any idea you could give me, and sorry for my bad English.
Github link: https://m-ribero.github.io/mubles-ballena/galeria.html
edit: Very important detail, it often gets fixed after reloading or resizing the page, but for the first time someone enters there, then it doesn't motivate people to invest more time in the site if it looks that bad.
gallery destroyed
gallery destroyed 2
The problem is with Masonry and not Fancybox (or any other lightbox alternative). Looks like it incorrectly calculates height for the container. Since it works after assets have been cached, I guess that your masonry script does all calculations before your CSS is loaded. Therefore top/bottom padding is not taken into account for calculations.
I use sly data-sly-resource="${# path='column-1-title', resourceType='wcm/foundation/components/text'}" to bake in the text-sightly component directly(cq:include tag also have the same problem). But after I authored the content of the text, a 404 error arises in the console. And the page can't be authored anymore until I reload the page.
CLICK HERE TO LOOK 404 NOT FOUND ERROR IMAGE
Try using:
resourceType='foundation/components/text'
We have also observed that using "'wcm/foundation/components/text'" has issues in TouchUI.
We need to specify a proper sling:resourceSuperType for the component that be baked in.
I have a big SVG document here, containing a map of all the quests in a certain online game. Each quest node is inside a SVG <a> element, linking to a distinct named anchor in a big HTML document that loads in another tab, containing further details about that particular quest. This works exactly as desired in desktop Safari, and I'd expect it to work just as well in any browser that supports SVG at all since I'm using only the most basic form of linking, but it fails badly on Mobile Safari (iOS 6) - which is my single most important browser target, considering that the game in question is for the iPad. It only scrolls to the correct anchor on the initial load of the HTML page; clicking a different quest in the SVG tab will cause a switch to the HTML tab, and the hash (fragment ID) in the address bar changes, but the page doesn't auto-scroll.
This appears to be a known limitation in Mobile Safari - hash-only changes in the URL apparently used to force a page reload, and that got over-fixed such that nothing gets triggered at all now. The fixes I've found online all seem to be applicable only in cases where the URL change is being generated programatically, from within the same document, rather than static links from a different document.
Further details:
I've tried doing the named anchors in both the old <a name="..."> form, and the newer <h1 id="..."> form. No difference.
I've tried adding an onhashchange handler, to force the scrolling to take place, but the handler isn't being called at all (verified by putting an alert() in it).
I could presumably fix the problem by having each quest's details in a separate HTML file, but that would severely affect usability - with all the details in a single file, you can use your browser's Find feature to search through them all at once. (Also, deploying 1006 files to my web hosting after each update would be a bit of a pain...)
Anybody have an idea for a work-around?
Is there any way to suppress the spinners and "transferring data" indicators that browsers show when a web page is loading?
I'm loading a document into a hidden iframe that will take a long time (10's of minutes). I don't want/need the user to be aware of this - it's just confusing to them to have the page look like it's still loading. SO I'd like to be able to disable all of the "page loading" activity that browsers normally show.
I eventually found a solution that will work for us. Instead of loading the document into a hidden iframe, we're using the "htmlfile" object described here:
http://cometdaily.com/2007/11/18/ie-activexhtmlfile-transport-part-ii/
This solves the problem on IE platforms. And on non-IE platforms, we can use XMLHttpRequest + CORS + chunk encoding.