Anyone know why my iOS app that uses a UIWebView which loads a form is ignoring all the form pattern and required rules? I don't think i need to post any code, as my app has many different forms all that work fine on any other browser.
For anyone looking the answer is here. UIWebViews do not support form validation or pattern rules.
html5 form validation not working in iOS UIWebView
Related
Trying to embed a pdf on my website like so:
<iframe src="filename.pdf" type='application/pdf' frameborder="0"></iframe>
The website is a rails site, and currently I'm only running it on a local server.
The problem is that the pdfs render with a toolbar on top and a sidebar with my adobe creative cloud account information, as seen in the picture below (the actual content of the pdf displays in the white box under the toolbar and to the left of the sidebar)
How can I get the pdf to render alone, without the menu and sidebar?
If you allow the browser to choose how the PDF gets rendered, you're never going to be able to create a consistent experience for your users unless you are in a controlled desktop environment.
If you are looking for a consistent experience, use pdf.js to render the PDF in the browser.
If you are in a controlled environment and all of your users have a browser/viewer combination that will let the browser show PDF using the Adobe Reader plugin (as your screen shot shows) then you can use the "open parameters" at the end of the URL to control what gets shown. See the documentation at the link below.
http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/pdf_open_parameters.pdf
That said, don't count on that solution to work for very long. Most modern browsers are not allowing the viewer plugins to function anymore and the rest are moving in that direction.
Searching more into stack, try that:
https://stackoverflow.com/a/2105095/7741129
For more detailed informations:
http://blogs.adobe.com/pdfdevjunkie/web_designers_guide
I think it's better use some kind of JS stuff just in case of cross-browser issues, like related into first link. Solutions like https://pdfobject.com/ it's helpful to get the job done. Look:
PDFObject 2.0 detects browser support for inline/embedded PDFs. (In
case you were wondering, your browser supports embedded PDFs. You
lucky dog, you!)
If you're working with dynamic HTML, such as a single-page web app,
you may need to insert PDFs on-the-fly. However, PDF embedding is not
supported by certain browsers. If you insert markup without first
checking for PDF support, you could wind up with missing content or a
broken UI.
The PDFObject utility helps you avoid these situations by detecting
support for PDF embedding in the browser; if embedding is supported,
the PDF is embedded. If embedding is NOT supported by the browser, the
PDF will NOT be embedded.
By default, PDFObject 2.0 inserts a fallback link to the PDF when the
browser does not support inline PDFs. This ensures your users always
have access to your PDF, and is designed to help you write less code.
The fallback link can be customized, or the option can be disabled if
you prefer.
PDFObject 2.0 is npm-ready. Modern web apps use npm to manage packages
and dependencies. PDFObject 2.0 is registered with Node Package
Manager (npm) and can be loaded dynamically.
PDFObject also makes it easy to specify Adobe's proprietary "PDF Open
Parameters". (Be warned these parameters are only supported by Adobe
Reader, most PDF readers will ignore the parameters, including the
built-in PDF readers in Chrome, Internet Explorer, and Safari. Read
more below.)
I have a webapp which is running perfectly well in most browsers, but I'm still trying to work out a few bugs which is preventing it from working correctly in iOS Facebook's in-app browser. Until I've got these sorted, I'd like to provide a message to give users the option to open the link in Safari.
The solution I have for now is to use javascript to detect the browser's user agent (similar to this question), and if it's the Facebook in-app browser, provide a message that the webapp is optimised for Safari and give instructions to copy and paste the link into Safari.
My question is this: is there a way to make a <a> tag open in a particular browser? I have seen questions like this one which seem to point to using target="_system" for Cordova apps, but is there a method to do this with html only?
There isn't a way to do this for Safari (using just HTML, anyway). For other browsers that have custom URL schemes, you could do it. For example, for Chrome you could have your link point to googlechrome://www.website.com.
The definitive answer: No, this is not possible.
As Andrew M mentioned, some browsers have some methods that do some things similar, but a pure html method to open a link in a generic browser does not exist.
I want to make a website that will only be accessible by people who use the link I put on the QR code.
Is such thing possible? Can a website recognize if the request is coming from html browser or mobile device?
No. Anyone could access the site via the same URL. You could try to use the user-agent string to try to limit access to mobile browsers, but a) this could prevent some mobile users from accessing the site, and b) all methods of detecting mobile browsers are easily spoofed.
My app is completely html CSS and JavaScript. I am running into a little problem because I would like the user to be able to use my webpage from the browser or use the app and maintain the cookies between the two.
Is this possible?
No, this is not possible because the WebBrowser control used in your hybrid app does not share anything with the Internet Explorer. They are completely separated and each one is sandboxed.
This also prevents other applications from reusing such cookies.
Here's the form in question
The "Email" button in the top right is just a mailto link, and it doesn't work in chrome's pdf reader. Any idea what's happening? It works just fine in acrobat.
It's unfortunately a limitation of the built-in PDF viewers in Chrome and Firefox. If you want the file to open in Acrobat, you have to force the browser to download the file rather than open it. You can do this in modern browsers using the HTML5 download attribute:
Download Form
This link has more details: http://davidwalsh.name/download-attribute
For a more widely compatible solution, you would have to use the Content-disposition header. It's possible to do this with PHP, there is an example here: How to force PDF to download beginner
It is simply a limitation of Chrome's PDF reader, possibly because of security reasons. The mailto link launches the installed email application and Chrome probably wants to avoid some problems.
I know this is an old thread, but it may help someone to keep in mind that mailto doesn't work in Chrome's PDF viewer (and in Adobe Acrobat Reader as well) if it has line break in it. Hyperlink has to be in one line!