Custom Slides Ignored; Stepper Ignores Steps
See original GitHub issuereact : 6.13.1 spectacle : 6.0.1
I’m trying Spectacle for the first time and ran into this issue Various Issues w/ Imported Slides #678, which mentions it should be resolved by the Slide
rewrite. I believe the rewrite has since been released, but the issue is not resolved so I’d like to reopen. Specifically, Slide
s are discarded if they are not inlined children of Deck
. The suggested workaround to wrap Slide
contents in React.Fragment
allows the Slide
to render, but causes nested Stepper
s to ignore their steps and immediately proceed to the next Slide
.
Please see this CodeSandbox I’ve prepared demonstrating the issues I’ve mentioned.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Custom Slides Ignored; Stepper Ignores Steps #871 - CodeSandbox
A simple Spectacle presentation sample for open source contributors to use to demonstrate behaviors in bug reports. 0.
Read more >Custom Components: Creating a Custom Stepper - Swift Talk
We work on the accessibility of our custom stepper component. ... By completely ignoring the contents of the stepper controls, ...
Read more >Angular Material Stepper component prevent going to all the ...
I want to prevent the user from visiting the next steps by clicking the step buttons of the stepper component. However, I want...
Read more >Stepper - Angular Material
Content for step label given by <ng-template matStepLabel> . Methods. isErrorState. Custom error state matcher that additionally checks for validity of ...
Read more >Sampler Synth Details in Logic Pro - Apple Support
Click the Details button to view or hide the Synth Details slide-out pane. ... Ignore Release Velocity button: Turn on to play samples...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@kale-stew This might be a related thing to #870 in that both
Appear
andStepper
are similarly written, and used here: https://github.com/FormidableLabs/spectacle/blob/88e635bae3a00eda9fd35bc77acb9d7ffe5a7b74/src/components/deck/index.js#L143-L144I can also confirm this behaviour. It appears that if you put any element or even a
React.Fragment
as a sibling, theStepper
component is then somehow happy and works as expected. Weird.