James Koster
James Koster
> I wonder if we should also update there That will probably be necessary to avoid falling foul of a11y requirements (visual order should match DOM order).
For the most part this is complete. We can open dedicated issues for outstanding pieces.
Thanks @jorgefilipecosta. I feel this better manages the prominence of this relatively obscure attribute. In the future it would be good to hide it altogether in favor of more intuitive...
Order is such an obscure attribute, and so rarely used, I don't know that we ever need to display it directly in the sidebar. If you're familiar with the feature,...
That approach would get my vote :)
Thanks @jorgefilipecosta, this is very cool :) Could we apply `__nextHasNoMarginBottom` to the range? Would it be feasible to define upper and lower bounds based on breakpoint? For example you'd...
Thanks Jorge, this is getting close and working pretty well. Would it be possible to update the display on container resize? One small issue currently is that; if you set...
Another tiny point, the values that appear as tooltips on the range don't really communicate anything useful, we can probably hide them.
Hey @jorgefilipecosta, I pushed a small update to the config. One issue is that the `default` value doesn't seem to apply at the xhuge breakpoint, which results in this broken...
That's an excellent suggestion @stokesman, thanks for pointing that out. I agree it's something that would improve the experience here. We should probably consider making that component public. @jorgefilipecosta I...