Skip to content

Commit b7ecaba

Browse files
committed
Update readme.md
1 parent 7be8b8b commit b7ecaba

File tree

1 file changed

+13
-4
lines changed

1 file changed

+13
-4
lines changed

readme.md

Lines changed: 13 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,10 +11,19 @@ MIT-style license: http://pipwerks.mit-license.org/
1111

1212
## Changelog
1313

14-
### 2.3, June 2023
15-
* Incorporated support for `navigator.pdfViewerEnabled`, which (as of Spring 2023) is now supported in all major browsers. This naturally led to redefining PDFObject's PDF support detection logic. If the browser is on a mobile device, PDFObject will automatically assume PDFs are not supported (as of June 2023, no mobile browsers properly support inline PDFs). If **not** a mobile device, PDFObject will check `navigator.pdfViewerEnabled`. If the feature is found, but _disabled_ (e.g. the user has intentionally disabled PDF support in the browser), PDFObject will respect this and behave as if inline PDFs are not supported. If `navigator.pdfViewerEnabled` is found and set to `true`, PDFObject will embed the PDF. If `navigator.pdfViewerEnabled` is not found, fallback logic will kick in and check what kind of browser is being used. If the browser is known to support inline PDFs natively (Chrome/Edge/Opera/etc, macOS Safari, Firefox), PDFObject will assume inline PDFs are supported and embed the file. If Internet Explorer, PDFObject will query against ActiveX for known PDF plugins (Acrobat, FoxIt) and act accordingly.
16-
* Removed `<embed>` in favor of `<iframe>`. PDFObject had previously defaulted to an `<embed>` element, but over time it has become apparent the superior solution is `<iframe>`. It's universally supported, and does not suffer from `<embed>`'s odd quirks and spotty support. This should make PDFObject more consistent and robust across platforms.
17-
* As a result of removing `<embed>` and redefining the detection logic, some PDFObject options have become obsolete. They are safe to keep in your code (will not throw errors), but are no longer used by PDFObject. The deprecated options are: `assumptionMode`, `forceIframe`, and `supportRedirect`.
14+
## 2.3 (February 2024)
15+
- Removed `<embed>` in favor of `<iframe>`. PDFObject had previously defaulted to an `<embed>` element, but over time it has become apparent the superior solution is `<iframe>`. It's universally supported, and does not suffer from `<embed>`'s odd quirks and spotty support. This should make PDFObject more consistent and robust across platforms.
16+
- As a result of removing `<embed>` and redefining the detection logic, some PDFObject options have become obsolete. They are safe to keep in your code (will not throw errors), but are no longer used by PDFObject. The deprecated options are: `assumptionMode`, `forceIframe`, and `supportRedirect`.
17+
- Incorporated support for `navigator.pdfViewerEnabled`, per #290. As of Spring 2023, `navigator.pdfViewerEnabled` is supported in all major browsers. This naturally led to redefining PDFObject's PDF support detection logic.
18+
- If the browser is on a mobile device, PDFObject will automatically assume PDFs are not supported (as of February 2024, no mobile browsers properly support inline PDFs).
19+
- If **not** a mobile device, PDFObject will check `navigator.pdfViewerEnabled`.
20+
- If the feature is found, but _disabled_ (e.g. the user has intentionally disabled PDF support in the browser), PDFObject will respect this and behave as if inline PDFs are not supported.
21+
- If `navigator.pdfViewerEnabled` is found and set to `true`, PDFObject will embed the PDF.
22+
- If `navigator.pdfViewerEnabled` is not found, fallback logic will kick in and check what kind of browser is being used.
23+
- If the browser is known to support inline PDFs natively (Chrome/Edge/Opera/etc, macOS Safari, Firefox), PDFObject will assume inline PDFs are supported and embed the file.
24+
- If Internet Explorer, PDFObject will query against ActiveX for known PDF plugins (Acrobat, FoxIt) and act accordingly.
25+
- Added support for converting base64 PDFs (string) to a downloadable file, per #243 and #270. This only impacts fallback content on browsers that don't support inline PDFs.
26+
- Improved handling of PDF Open Parameters. Ensures proper sequencing of parameters in URL string, per Adobe spec. Ensures `page` is always set if `comment`, `viewrect` or `highlight` are specified.
1827

1928
### 2.2.12, June 2023
2029
Refactored one line of code to restore IE11 compatibility, per #287.

0 commit comments

Comments
 (0)