Support component for prev and next buttons
See original GitHub issueHi, @lokyoung
I saw that you remove support for prevContent
and nextContent
slots after 1.9.5 version.
You replaced it with using next-text
and prev-text
props (using html there).
But now I can’t use custom components for these buttons.
Can you revert prevContent
and nextContent
slots?
Thanks!
Issue Analytics
- State:
- Created 5 years ago
- Reactions:18
- Comments:6
Top Results From Across the Web
How create separate component for prev/next buttons ReactJS
To answer your first question I just made two very simple functional components called Prev and Next. They get rendered within the Main ......
Read more >How to Add Prev/Next Buttons to Tab Component - Webflow Tips
Today, I present another tutorial on how to add Prev/Next buttons to a Webflow Tab Component, and make it function like a slider....
Read more >Navigation Components for Help Center (Table of Contents ...
To show/hide the Prev and Next buttons, go to the Guide admin panel and click “Customize design”. Choose the theme for which you...
Read more >How To Create Next and Previous Buttons - W3Schools
Well organized and easy to understand Web building tutorials with lots of examples of how to use HTML, CSS, JavaScript, SQL, Python, PHP,...
Read more >ARIA: button role - Accessibility - MDN Web Docs
Adding role="button" tells assistive technology that the element is a button but provides no button functionality. Use <button> or <input> with ...
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
I install old version and it work …
Hey, i’m also trying to understand why this was removed.
Most vue codebases have icon components or custom buttons that need to be passed to this kind of plugin slots, instead of relying on css trickery.
If still want to allow raw html to be passed as prop just conditionally display the slot:
A more ugly, but working approach if you don’t want the extra ‘span’ (computing attributes and events into computed props and using
v-bind
andv-on
would clean it up)Then
A more radical approach
As i’ve mentioned besides “custom content”, we might want to pass a custom link entirely from our own design system/framework. For that we could expose the methods and attributes via slot-scope.
Contributing
The package seems unmaintained judging by the repo activity. It’s fine, i also have my own unmaintained plugins, but just probing if should just fork or if there’s plans to future releases or updates.
Cheers ✌️