auto-slide duration falls back on global setting instead of looking a…

…t first fragment
boycaught · Jun 16, 2023 · 12f5ba4 · 12f5ba4
1 parent 227f90f
commit 12f5ba4
Show file tree

Hide file tree

Showing 5 changed files with 4 additions and 8 deletions.
diff --git a/dist/reveal.esm.js b/dist/reveal.esm.js
diff --git a/dist/reveal.esm.js.map b/dist/reveal.esm.js.map
diff --git a/dist/reveal.js b/dist/reveal.js
diff --git a/dist/reveal.js.map b/dist/reveal.js.map
diff --git a/js/reveal.js b/js/reveal.js
@@ -2205,10 +2205,6 @@ export default function( revealElement, options ) {
 
 			let fragment = currentSlide.querySelector( '.current-fragment' );
 
-			// When the slide first appears there is no "current" fragment so
-			// we look for a data-autoslide timing on the first fragment
-			if( !fragment ) fragment = currentSlide.querySelector( '.fragment' );
-
 			let fragmentAutoSlide = fragment ? fragment.getAttribute( 'data-autoslide' ) : null;
 			let parentAutoSlide = currentSlide.parentNode ? currentSlide.parentNode.getAttribute( 'data-autoslide' ) : null;
 			let slideAutoSlide = currentSlide.getAttribute( 'data-autoslide' );