pptx-angular-viewer 1.1.50 → 1.1.52

package/CHANGELOG.md

@@ -4,6 +4,12 @@ All notable changes to this project are documented here.
 This file is generated from [Conventional Commits](https://www.conventionalcommits.org)
 by [git-cliff](https://git-cliff.org); do not edit it by hand.
 
+## [1.1.51](https://github.com/ChristopherVR/pptx-viewer/releases/tag/pptx-angular-viewer@1.1.51) - 2026-06-27
+
+### Bug Fixes
+
+- Missing document links (by @ChristopherVR) ([f52bd6f](https://github.com/ChristopherVR/pptx-viewer/commit/f52bd6fd2fc4f564f018ecf5e84e64d24c8fd240))
+
 ## [1.1.45](https://github.com/ChristopherVR/pptx-viewer/releases/tag/pptx-angular-viewer@1.1.45) - 2026-06-25
 
 ### Other

package/README.md

@@ -12,7 +12,7 @@ as real HTML and CSS with full editing and export support.
 
 The rendering is done by the framework-agnostic [`pptx-viewer-core`](https://www.npmjs.com/package/pptx-viewer-core) engine (also published as [`@christophervr/pptx-viewer`](https://www.npmjs.com/package/@christophervr/pptx-viewer) -- the two names are identical releases), which turns a `.pptx` file into a structured slide model. This package is the Angular layer that draws that model on screen, and the engine is **bundled in**, so you install just one package.
 
-<samp>**[▶️ Try the live demo](https://christophervr.github.io/pptx-viewer/demo-angular/)** · **[📦 npm](https://www.npmjs.com/package/pptx-angular-viewer)** · **[📖 Full docs](https://christophervr.github.io/pptx-viewer/)**</samp>
+<samp>**[▶️ Try the live demo](https://christophervr.github.io/pptx-viewer/demo-angular/)** · **[📦 npm](https://www.npmjs.com/package/pptx-angular-viewer)** · **[📖 Full docs](https://christophervr.github.io/pptx-viewer/)** · **[🧩 Core SDK](https://www.npmjs.com/package/pptx-viewer-core)**</samp>
 
 > **[▶️ Try the live demo](https://christophervr.github.io/pptx-viewer/demo-angular/)**: open a `.pptx` and render it in your browser, no install required.
 
@@ -164,19 +164,17 @@ async save() {
 ## Limitations
 
 The Angular package has reached functional parity with the React package: all 11
-element types render; the full Tailwind 4 Office ribbon is wired; editing,
-presentation, export, collaboration, comments, and mobile chrome all work. The
-remaining items are polish/cosmetic, not behavioural gaps:
-
-- **Master/template editing** - Editing routes to slide elements only; edits to
-  the slide master or layout template are not yet wired.
-- **Eyedropper on Firefox/Safari** - Angular uses the native `EyeDropper` API;
-  React adds a rasterize-and-sample fallback for browsers that don't support it.
+element types render; the full Tailwind 4 Office ribbon is wired; editing
+(including slide master/layout template editing), presentation, export,
+collaboration, comments, and mobile chrome all work. The remaining items are
+polish/cosmetic, not behavioural gaps:
+
 - **Pixel-level cosmetic differences** - Some toolbar controls are not pixel-
   identical to their React counterparts (spacing, split-button affordances,
   dropdown chrome).
-- **3D models** - GLB/GLTF models fall back to their poster image (requires
-  optional Three.js peer dependencies).
+- **3D models need the Three.js peer** - GLB/GLTF models render interactively when
+  the optional `three` peer dependency is installed, and fall back to their poster
+  image otherwise (the same as the React package).
 
 The `pptx-viewer-core` engine parses all element data, so you can access it from
 the model even where the UI does not expose it yet. Progress and design notes live