@barklund I understand what you are saying and agree in regards to separation of concerns. I would say that I would think the intent of modifier was to provide some canned classes and an easy way to implement them with exposing contradicting user styling via the style attribute.
I would be interested in why, as far as SoC goes, you think using style="classname" is worse than using modifier="classname"? In my opinion, they are the same thing. Now, I would agree that if the Onsen team implements something for one element, it would be nice for it to be consistent across all the elements.
Having said that, since navigator is their base navigation element (like the carousel), they are consistent in not having modifier.
When item-width < 100%, it seems the first and last carousel items can’t be ‘selected’ (meaning the postchange event doesn’t fire for these elements).
As a workaround, I’m thinking along the lines of adding dummy items on each end of the carousel, and maybe detecting these edge items as an overscroll rather than a postchange (not sure if this would work, I haven’t had time to test this yet), and handle that event in order to automatically re-select the nearest non-dummy item.
Are there any known workarounds?
edit: My workaround idea doesn’t work right. The carousel kind of settles on the first or last list element, as if it was selected, without it actually being selected in terms of activeIndex/postchange, nor is overscroll triggered unless the user goes out of his/her way to do it.