3 ms·

Doesn't work correctly in firefox, the items overlap and cannot be re-ordered, sometimes they pop outside the container completely. It's a shame, I was looking

by retox 5y ago

Doesn't work correctly in firefox, the items overlap and cannot be re-ordered, sometimes they pop outside the container completely. It's a shame, I was looking for something like this recently. https://i.postimg.cc/HnQZsjkD/drag.png https://i.postimg.cc/HnQZsjkD/drag.png

kevincox 5y ago
Worked fine for me on Firefox 89.0.2.
jimmy2020 5y ago
Keep in your mind that I need feedback, that’s why I am taking the risk of publishing the demo without adding scrolling yet. There’s a reason, I am desperate for a feedback. I know it can be buggy but this is every software with a new concept. With that being said, I don’t push to production without testing at all. I am sorry to have such a bad experience, still, I am asking you to give it a second chance and look deeper into the API. Bugs can be fixed but concepts can’t. I welcome any issues and I’ll be happy if you open one. (https://github.com/dflex-js/dflex https://github.com/dflex-js/dflex)
- retox 5y ago
  I'm sorry, I didn't mean to sound as dismissive as I my comment came across, I didn't have a lot of time to reply at the time. I can put together a video and better description of the problem if you like. All I did was grab the purple divs and drag them around randomly, things were working for a few drops then everything looked to get out sync.
  - retox 5y ago
    It seemed more robust today, not sure if you pushed an update. The problem seem to happen when dragging and dropping quickly, feels like the drop event isn't firing every time so the item gets stuck to the cursor then when it does fire next time you drag you 'pick up' more than one item.
    - jimmy2020 5y ago
      The problem with the DFlex approach is it calculates coordinates and positions internally without calling browser API. While this approach considers very lightweight and allows to scale the number of interacted elements without causing any problem it has a trade-off. If one number is calculated wrong it affects all other node dependencies. One solution to this problem is considering a save mode to minimize error boundaries. Anyway, I'll investigate it and see where things go wrong. Thanks for your feedback, I appreciate it.
  - jimmy2020 5y ago
    > I can put together a video and better description of the problem if you like. Yes please, I can't fix the bug without being able to test it and reproduce it step by step so I can detect what went wrong.

by retox 5y ago

kevincox 5y ago

Worked fine for me on Firefox 89.0.2.

jimmy2020 5y ago

Keep in your mind that I need feedback, that’s why I am taking the risk of publishing the demo without adding scrolling yet. There’s a reason, I am desperate for a feedback. I know it can be buggy but this is every software with a new concept. With that being said, I don’t push to production without testing at all. I am sorry to have such a bad experience, still, I am asking you to give it a second chance and look deeper into the API. Bugs can be fixed but concepts can’t. I welcome any issues and I’ll be happy if you open one. (https://github.com/dflex-js/dflex https://github.com/dflex-js/dflex)

retox 5y ago
I'm sorry, I didn't mean to sound as dismissive as I my comment came across, I didn't have a lot of time to reply at the time. I can put together a video and better description of the problem if you like. All I did was grab the purple divs and drag them around randomly, things were working for a few drops then everything looked to get out sync.
- retox 5y ago
  It seemed more robust today, not sure if you pushed an update. The problem seem to happen when dragging and dropping quickly, feels like the drop event isn't firing every time so the item gets stuck to the cursor then when it does fire next time you drag you 'pick up' more than one item.
  - jimmy2020 5y ago
    The problem with the DFlex approach is it calculates coordinates and positions internally without calling browser API. While this approach considers very lightweight and allows to scale the number of interacted elements without causing any problem it has a trade-off. If one number is calculated wrong it affects all other node dependencies. One solution to this problem is considering a save mode to minimize error boundaries. Anyway, I'll investigate it and see where things go wrong. Thanks for your feedback, I appreciate it.
- jimmy2020 5y ago
  > I can put together a video and better description of the problem if you like. Yes please, I can't fix the bug without being able to test it and reproduce it step by step so I can detect what went wrong.