@tienlbhoc Look at “load more” functionality (onInfiniteScroll, without lazyRepeat). That’s a better way to deal with async calls. Otherwise, in delegate.createItemContent you can synchronously return an empty new item and then asynchronously modify its content when the data is ready.
I’m not sure if this is inherently known, but it’s important to note that when using the confirm notification, we must know which option the user has chosen to execute logic based on the response. In the options.callback we need to identify (document) the parameter for a positive or negative response. Such as:
@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.