This may have been covered but will PaySnap work with Elements or will I need to use another payment front end?
Thanks,
RJ
Hi @RobertJames
No, PaySnap is a stack and stacks will not work in RapidWeaver Elements. You will want to find another solution to add buy now and shopping cart buttons to your website.
Both PayPal and Stripe offer their own buttons you can embed, or you can go with a more fully featured shopping cart that is embeddable. There are several good ones to choose from.
I want to update but I’m scared 
I have several projects now built in Elements and don’t want to mess anything up and cause more work for myself. I see the “Danger Zone” message and chicken out…lol
3 Likes
I like the Tab component as well, and it is going to be very useful. But it appears to have issues when you are on mobile. If there are more than two tabs, they will run off the edge of the screen, forcing you to scroll horizontally to see them.
Is this the intended behavior on mobile, or am I missing something?
1 Like
I was actually really looking forward to the tab component, as I’m still using it on an old RapidWeaver Classic website.
Unfortunately, in its current state it’s not really usable on mobile. In my RapidWeaver Classic version, the tabs behave much better on small screens: if there isn’t enough space, either a maximum of two tabs are shown next to each other, or they are stacked vertically one below the other.
I would therefore really appreciate an adaptation of the tab component specifically for mobile use.
What would be the ideal way for the tabs to behave on Mobile? Would you like them to be scrollable, stackable, or something else?
I’m interested to hear what solution people would like us to implement 
P.S. I have now created a ticket for this issue.
EDIT: After looking into this further, we think the best option is probably to stack the tabs on mobile.
1 Like
As a basic version, it would probably be best if the tabs behaved responsively in the same way as the Filter Tag component. Ideally, users should also be able to define themselves whether they want 2–3 tabs per row or just a single tab per row.
That’s how the tabs currently work on my RW Classic site.
In a PRO version, the component could potentially be enhanced—if there is demand from the community—with vertical tabs and additional features.
Check the 2.0 Beta email there is a link to one. You have to of installed the Beta first though.
if you set Overflow to scroll they scroll from off screen but the content also scrolls, wrap seems a good solution as long as there not too many and the content is off screen, turning into a drop-down menu?
In my head I have four horizontal tabs on desktop. Could probably squeeze them in on mobile if I don’t use big words but having them stacked vertically (if that is what you meant) would probably be better.
As I think about this more however as you scroll the tabs are quickly going to go off the top of the page so to change tabs I would have to go back to the top of the page whereas as it is now with the pages listed in the sticky menu I don’t need to.
Still very much like the idea of tabs on the desktop but not seeing it work for me on mobile. Elements has made me think more about how my site looks on mobile and I have duplicated and edited a lot of components so I can hide or unhide depending on screen size. Tabs might be a step too far I think in following the same process. Will have to think of something else to do now this long weekend.
I’ve also thought a lot about how tabs could work best on mobile.
A hybrid between tabs and a slider would probably be the optimal solution for mobile.
2 Likes
okay… So while Tabs can be useful in certain scenarios, from a UX and accessibility standpoint they’re often not the best default choice.
Web pages scroll vertically, which users are extremely good at. Stacked content is easier to scan, and easier to navigate, it also avoids hiding information behind interactions that aren’t always obvious or discoverable (for some users).
In short, be carful when and how you use tabs 
Agree. I did a fair amount of prototyping of one idea and came to the same conclusion.
However, back when we designed Go PenPoint, the first product with tabs, we also developed the notion of “overlapping tabs.” If the space was constrained so that the tabs couldn’t all fit, the current tab was fully opened and the others were overlapped and only partially visible.
If the user knew they were in a tabbed section, swiping left and right would go to other tabs.
Stackable for sure
or I prefer menu, laws of physics space
didnt like full width dropdown
3 Likes
nice 
I did not know that and I assume a lot of users don’t know that. I thought you would have to click on the tab.
I was intending to use tabs instead of second level navigation to avoid having to go to the top menu and then look at the second level titles. Thinking I won’t bother with tabs now. Would be nice to have an option for the second level navigation to be laid out horizontally rather than vertically. Maybe there is and I have not found it yet. Anyway, taking this off topic so will shut up.
Hi, I’m a relatively fresh user.
In 2.0 I can’t find the ‘edit text’ option in the typography and button component. HAs something changed or is this a bug?
Also, when using dropzones in a custom components… I’d like to drop in a modal. It doesn’t trigger however.
@dan Quick question… I typically don’t download betas because I can not risk the data on my site getting corrupted. Is this beta stable enough that I don’t need to worry about that, or should I wait for the gold master release?
1 Like