Filed under user interfaceShow All
Examples and documentation can be found at https://pdfobject.com.
Copyright (c) 2008-2023 Philip Hutchison MIT-style license: http://pipwerks.mit-license.org/
2.2.12, June 2023
Refactored one line of code to restore IE11 compatibility, per #287.
2.2.11, May 2023
Typo in version number within PDFObject code. Yup, I'm a bit rusty.
2.2.10, May 2023
Version bump for cleaning up docs and aligning on NPM. I'm a bit rusty.
2.2.9, May 2023
- Fixed regression for
pdfOpenParamshandling, resolves issue #272. Hat tip to Theo Beers.
- Added ability to specify custom attribute on
iframeelements, per #274
2.2.8, April 2022
- Refactored to reduce redundant code. Simplified iframe and PDFJS handling. Subsequently resolves #263 (double scroll bars) and PR #267 (PDFJS_URL param fix). Hat tip to Theo Beers, Sascha Greuel, meier-andersen, and everyone who helped identify and confirm the underlying issues.
fallbackLinkhandling to ensure
falseis respected. Hat tip to Theo Beers.
2.2.7, September 2021
titleattribute to PDFJS
iframeelements per #258
2.2.6, July 2021
iframeelements per #248
- Force Safari desktop to embed via iframe due to freezing bug in macOS 11 (Big Sur) per #243
- Fixed version number per #247
- Added note about documentation to readme file per #251
2.2.5, March 2021
- Expanded assumptions to counteract Chrome's deprecation of MIME type checks. Any 'modern' browser will be given a green light regardless of whether
assumptionModeis enabled. However
assumptionModewill still be available for browsers that are not declared modern.
allow="fullscreen"attribute to iframe embeds, in case anyone needs their PDFs to be rendered fullscreen.
- Fixed Firefox user agent sniffing for edge case (thanks to David Novodchuck for the PR)
2.2.4, October 2020
windowto play nice with React and NextJS.
2.2.3, September 2020
Version bump for NPM. Sigh.
2.2.2, September 2020
Fixed typo affecting
suppressConsolefunctionality. Hat tip to John Hunter for the discovery and fix.
2.2.1, September 2020
Fixed typo affecting styling of iframe when forcing PDFJS.
2.2.0, September 2020
- New behavior: Dropping support for IE9 and IE10, which have practically 0 marketshare now.
- New behavior: Now explicitly displaying fallback content for all mobile devices, even "Request Desktop" version of pages in iOS. The reasoning is simple: As of the time of this update, no mobile device (Android, iOS) natively supports embedded PDFs. This change will lead to a consistent experience across all mobile devices. PDFs can be rendered via PDF.js on mobile if embedding on mobile is a critical need. PDF.js is not included with PDFObject.
- New option: Omit inline styles by setting option
true. This helps developers who use strict environments where inline styles are not allowed. Note you will be responsible for applying proper styling via your own CSS.
- New option: Suppress console logging by setting option
true. PDFObject currently places error messages in the console if the PDF can't be embedded for some reason. This option allows you to mute those alerts.
- New option: Force PDFObject to embed the PDF in an iframe (instead of an
<embed>) by setting
- Refactored to use more modern code conventions, such as
letin lieu of
el.classList.add()in place of
el.className = 'foo', and
myvar === undefinedin place of
typeof myvar === "undefined". Implemented a
letdeclaration before each variable instead of the Crockford practice of one
- New option: On macOS systems, Safari does not properly embed PDFs that have been requested via 302 URL redirection when embedding using the
trueforces PDFObject to use an
<iframe>instead of an
<embed>for desktop Safari. Hat tip to John Hunter for the discovery and fix.
- Refactored to make code safer for server-side node.js-based environments.
- Refactored to eliminate string-based element creation via
innerHTML. Replaced with standard DOM methods. This helps alleviate unforeseen issues with file names. Only exception is insertion of fallback content, which is passed as a string via
- Removed iframe scrollfix for iOS, as it is no longer needed as of iOS13. iOS 12 and lower have ~5-7% marketshare and shrinking fast.
- Refactored codebase to make it more concise and legible.
2.1.1, October 2018
Improved handling of iOS to properly indicate iOS does not support embedded PDFs.
2.1, October 2018
assumptionModedefault from false to true. This will ensure PDFObject 2.x will work for Firefox users without requiring them to change their codebase to enable assumptionMode. All they need to do is load the latest version of PDFObject, the PDFObject utility will take care of the rest.
2.1 (dev branch)
January 2017: Modified to support Mozilla's removal of
assumptionModefor manual override of PDFObject's default
2.0, April 2016
Initial release of PDFObject 2.0. Contains breaking changes, and is not compatible with PDFObject 1.x.
- Fixed regression for