Dan van Zyl - 2 hours ago
  • Description has changed:

Diff:

--- old
+++ new
@@ -1,7 +1,7 @@
-Problem
+**Problem**
 If a KnowledgeDesk topic contained a standard link to a YouTube video, the `topicFrame` would attempt to load YouTube directly. Because YouTube enforces strict `X-Frame-Options: sameorigin` security headers, the frame displayed a "www.youtube.com refused to connect" error, and the browser console filled with `SecurityError` messages. Users had to click "Back" to return to the documentation.

-Fix
+**Fix**
 interceptIframeLinks() in viewer.js now explicitly catches any link containing youtube.com or youtu.be. It prevents the frame navigation entirely and forces the link to open in a new browser tab via window.open().

 Effect