Muuri: Should grid.synchronize() method be deprecated?

Created on 4 Sep 2019  路  3Comments  路  Source: haltu/muuri

For the next release I've been reviewing a lot of Muuri's core functionality and reorganizing things. Part of this process has included dropping the _fat_ from the internal/public API. Personally I've never actually needed to use grid.synchronize() method and been wondering if anyone is using it all. If you have needed grid.synchronize() method I'd be very interested to hear some real-world use case scenarios.

If it turns out that nobody's is using it for anything I think it should be deprecated. It's one of those API methods that I initially planned for _potential_ future usage, but haven't really been finding usage for it.

help wanted question

Most helpful comment

We use the synchronize() method for accessibility purposes. If the layout is changed after dragging an item, the DOM needs to be updated to ensure that tab order is maintained.

All 3 comments

We use the synchronize() method for accessibility purposes. If the layout is changed after dragging an item, the DOM needs to be updated to ensure that tab order is maintained.

Yep, let's not deprecate 馃憤

We use the synchronize() method for accessibility purposes. If the layout is changed after dragging an item, the DOM needs to be updated to ensure that tab order is maintained.

@abishekreddy do you have an implementation of setting tabindex for accessibility purposes you could share, please? I'm needing to do this too.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

PrestaShark picture PrestaShark  路  7Comments

bsherwoodofdaptiv picture bsherwoodofdaptiv  路  4Comments

emilime93 picture emilime93  路  5Comments

dedurus picture dedurus  路  4Comments

ppwfx picture ppwfx  路  4Comments