5 ms·

Yep sliders aren't quite baked yet. Should work on chrome. Thanks for reporting. https://github.com/wiredjs/wired-slider/issues/3 https://github.com/wiredjs/wir

by shihn 8y ago

Yep sliders aren't quite baked yet. Should work on chrome. Thanks for reporting. https://github.com/wiredjs/wired-slider/issues/3 https://github.com/wiredjs/wired-slider/issues/3

Tijdreiziger 8y ago
FYI, the slider doesn't work at all on Chrome Android.
- myguysi 8y ago
  Same on Safari iOS
  - shihn 8y ago
    Slider is fixed now.
    - 131012 8y ago
      There are still minor issues. The roughness slider disappeared when I slid it all the way to the right (on Firefox 60). But good work anyway, the results are really nice!
    - asdsa5325 8y ago
      Can confirm, thanks!
- shihn 8y ago
  Yep not very touch friendly at the moment. Bug filed
intrasight 8y ago
The fact that your designs "don't work" is very disconcerting - given that we've spent 20 years trying to separate function from design. Does this mean that after 20 years that we still don't have a good clean separation?
- intrasight 8y ago
  Not knocking the design in any way. Just expressing frustration and sadness that you've even have to think about function.
  - arbie 8y ago
    This library is great, although I don't understand your frustration. An interactive mockup library with broken interaction is a bug, no?
    - kbenson 8y ago
      I think the point is that if the function and design were actually separate, a non functioning element would also be non functioning in plain HTML (no/little design). That would be much easier to spot, and wouldn't even really be the designers problem. It's understandable why it happens here, the browser can't easily provide this design with pure HTML and CSS, so javascript and SVG are likely carrying some of the load, and bugs there are causing problems. That said, one of the main benefits of separating function and design is that this stuff isn't supposed to happen, or be much more rare at least, so it is sad that to utilize this we have to introduce those problems again.
- uryga 8y ago
  Another comment in this thread mentioned a similar project, a Swing "napkin" theme, which managed a rough look as normal styling. So I guess Swing did something better than HTML/CSS - from skimming the comments i gathered that this library had to reimplement everything from scratch using SVG/Canvas.
  - pjmlp 8y ago
    Web components are still trying to catch up with the components market that native apps enjoy since the 90's. I guess we still need a few more years of catching up.

by shihn 8y ago

Yep sliders aren't quite baked yet. Should work on chrome. Thanks for reporting. https://github.com/wiredjs/wired-slider/issues/3 https://github.com/wiredjs/wired-slider/issues/3

Tijdreiziger 8y ago

FYI, the slider doesn't work at all on Chrome Android.

myguysi 8y ago
Same on Safari iOS
- shihn 8y ago
  Slider is fixed now.
  - 131012 8y ago
    There are still minor issues. The roughness slider disappeared when I slid it all the way to the right (on Firefox 60). But good work anyway, the results are really nice!
  - asdsa5325 8y ago
    Can confirm, thanks!
shihn 8y ago
Yep not very touch friendly at the moment. Bug filed

intrasight 8y ago

The fact that your designs "don't work" is very disconcerting - given that we've spent 20 years trying to separate function from design. Does this mean that after 20 years that we still don't have a good clean separation?

intrasight 8y ago
Not knocking the design in any way. Just expressing frustration and sadness that you've even have to think about function.
- arbie 8y ago
  This library is great, although I don't understand your frustration. An interactive mockup library with broken interaction is a bug, no?
  - kbenson 8y ago
    I think the point is that if the function and design were actually separate, a non functioning element would also be non functioning in plain HTML (no/little design). That would be much easier to spot, and wouldn't even really be the designers problem. It's understandable why it happens here, the browser can't easily provide this design with pure HTML and CSS, so javascript and SVG are likely carrying some of the load, and bugs there are causing problems. That said, one of the main benefits of separating function and design is that this stuff isn't supposed to happen, or be much more rare at least, so it is sad that to utilize this we have to introduce those problems again.
uryga 8y ago
Another comment in this thread mentioned a similar project, a Swing "napkin" theme, which managed a rough look as normal styling. So I guess Swing did something better than HTML/CSS - from skimming the comments i gathered that this library had to reimplement everything from scratch using SVG/Canvas.
- pjmlp 8y ago
  Web components are still trying to catch up with the components market that native apps enjoy since the 90's. I guess we still need a few more years of catching up.