Promising, but a little rough around the edges

  • ooksanen

    (@ooksanen)


    7 months ago

    Really nice start. I’ve tried doing something quite similar, but this is a much nicer approach than what I’ve come up with. Few rather major gripes, though:

    1. Editor view breaks when enabling a carousel. Looks like it’s due to following CSS declaration:
      :has(.abcs) {
      position: relative !important;
      }
      which messes the editor sidebar positioning / scroll.
    2. I’m not a huge fan of the pure CSS approach using ::scroll-button and ::scroll-marker as those are not yet supported by Safari and Firefox.

    Other than that I really like the idea and code looked good too. Keep up the good work!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support supportweblazer

    (@supportweblazer)

    7 months ago

    Hi, many thanks for your support, I will try to improve the plugin soon,
    I want to use pur CSS but there is still some limitations.
    I work on this plugin by my own for free so if you want to help me please consider give it 5 star.
    Many thanks

    Plugin Support supportweblazer

    (@supportweblazer)

    3 months, 2 weeks ago

    Hi @ooksanen,

    I wanted to personally reach out and let you know that we have just released a major update (v2.0.0) that completely addresses all the issues you highlighted in your review!

    Here is what we have done:

    1. Complete Cross-Browser Compatibility: We completely retired the experimental CSS ::scroll-button and ::scroll-marker pseudo-elements. They have been replaced by standard HTML buttons and dot indicators powered by an ultra-lightweight Vanilla JS engine (<5kb) with zero dependencies. The carousel now works smoothly and consistently on Firefox, Safari, Chrome, Edge, and all mobile browsers.
    2. Gutenberg Layout & Sidebar Fixes: We have thoroughly redesigned the editor CSS integration. The broad :has() selector rules that interfered with Gutenberg’s sidebar layout and canvas scrolling have been removed and precisely scoped. The block editor now behaves perfectly without any side-effects on the WordPress UI.

    If you have a moment, we would love for you to update to the latest version and give it another spin. If you feel these major improvements have made the plugin much better, we would be incredibly grateful if you would consider updating your rating.

    Thank you again for your constructive feedback—it was crucial in helping us make this plugin better for everyone!

    Best regards

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this review.