primereact icon indicating copy to clipboard operation
primereact copied to clipboard

Published 20 hours ago • verified publisher icon primefaces

SpeedDial: Nesting SpeedDial not working

Open xAl3xFx opened this issue 1 year ago • 3 comments

Describe the bug

Nesting a SpeedDial component as a part of the model option's of another SpeedDial is not working properly. In the Reproducer you can see that the nested SpeedDial is being opened when the outer SpeedDial gets clicked. Also it's not responsible and clicking on it is not closing it as well.

Reproducer

https://stackblitz.com/edit/5ikcer?file=src%2FApp.jsx

PrimeReact version

10.5.1

React version

18.x

Language

ALL

Build / Runtime

Create React App (CRA)

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

xAl3xFx avatar Mar 15 '24 10:03 xAl3xFx

I am not sure what your design goal is with nested dial's so I will let PrimeTek answer...but a few thoughts.

  1. I don't think SpeedDial's were designed to be nested.
  2. Just from a pure UX perspective its an odd and unexpected user experience. Have you ever seen something like a Speed Dial nested on any other website out there?

melloware avatar Mar 15 '24 11:03 melloware

Hi! I see your point I haven't seen any other site using such mechanism. Here are my reasons to want this thing:

  1. I need this feature for a closed business project where everyone using the project is well aware of it's functionalities.
  2. I am mainly using the SpeedDial as an 'operations' column in DataTable components. The thing is that there is a particular DataTable that has so many operations that it becomes unusable. Since some of this operations are logically related to each other my idea is to group them together. Imagine the operations column is the last column of the table and it is just a SpeedDial button. It expands to the left and there are like 10 buttons. What I want to do is group 5 out of this 10 buttons in one SpeedDial which will expand down. I agree that this is bad UX and everything, but this is how the whole system was designed so not much to do here.
  3. I will understand if you decide that this is something that is not expected to work by design and decide to close this issue.

Thank you for your time. Wish you all the best!

xAl3xFx avatar Mar 15 '24 14:03 xAl3xFx

No worries I totally get it. If you want to debug it it does seems strange both are responding to the same button click.

melloware avatar Mar 15 '24 14:03 melloware