So perhaps I am doing something wrong. I am observing that eventListeners are piling up. Here is my situation. I tap a button, which causes a pushPage to occur. In the new page, add an eventListener. Later, the page gets popped. If I pushPage to the page again, an additional eventListener is created. The old event listener isn’t removed when a page is removed from the DOM. I see this using Chrome Dev tools. My question: should Onsen do this for me, or am I expected to manage this myself?

Is it possible to “scroll” to an item that has been removed from the DOM due to the lazy system? Or, more specifically, in my case, I might add an item to the data set that feeds the lazy list, but due to what part of the list I am viewing, the added item may not appear in the DOM after a lazy.refresh. I would like to progmatically “scroll” to a specific item that I just added, even if that item isn’t in the DOM. The reason: when an item is added, I want to view the list so that I can see and flash the list item that was just added to the data. It would be neat if there was a method such as .goto(index). From what I can tell, there is not.

So, I ended up just doing a little hack to adjust the minimum height of the popover. Taken from my css mod file:

/* onsen-ui normally sets this at 100px.  that means you can't have a popup menu of just one list-item.  this change fixes that. */
.popover__content{
	min-height: 				0px;
}

Works for me.

Hi. I have the following code. It is a popover that covers a “md-more” toolbar button. It only has one list-item, but the popover seems to require two at a minimum and forces spaces for two. Please see screenshot for example output. I am using Onsen 2.8.3, but I’m not ready to upgrade at this point, so I don’t know if it’s still an issue or not.

<ons-popover ... cover-target cancelable>
	<ons-list>
		<ons-list-item tappable>
			Delete
		</ons-list-item>
	</ons-list>
</ons-popover>

Hello,

Maybe I’m missing something, but how can I change the GestureDetector’s holdTimeout property without editing the onsenui.js file?

If I understand the problem, I also have a situation like this. My login screen doesn’t need the splitter menu. But it doesn’t need a toolbar either. I first played with just removing swipeable, but later decided to keep my login page simple, and use “window.location = file.html” instead to go to the main page that has the splitter and everything.

@Fran-Diox I agree, but not entirely. I feel there is a legitimate reason to have a notification window prevent the device back button from working. FOr example, my app might alert the user, “Hey stupid, pay up or your account is deleted tomorrow!”. I’m sure you’re like me and probably everybody else on the planet, you’ve hit the back button on a notification in “real” apps out of instinct without ever reading them. Very much like clicking “Accept” without reading the EULA for a program. But some notifications should be purposfully interacted with, such as my example. The user should not be able to click outside the notification box to close it, and should not be able to click the device back button to close it… instead, the user should b required to click “OKAY” or whatever the notification button is.

But, even if we disagree with expected behavior, I think there is one thing that seems natural: if I have a non-cancelable notification visible, hitting the device back button causing the app to close doesn’t make sense. If the notification is cancelable=false, and you hit the device back button, the app closes… that seems the exact opposite of cancelable, but on a larger scale… instead of “not canceling” the notification, it cancels the app.

@Michael-Redwine As an update, I discovered that this problem doesn’t manifest itself if I set cancelable:true. If I do that, the back button closes the dialog. If I don’t set that, it closes the app.

Expected behavior: device back button does nothing until user dismisses the alert by pressing “OK” (or whatever the button says).

I am observing a bit of a problem. For testing purposes, I have two pages. A button on page one pushes page two, and this is fine. When deployed to my Android, the back button works as expected: if on page 1, the app exits. If on page two, it goes back to page one. However…

On page two, on “focusout” of an ons-input, I have jquery perform an ajax call to my web server to receive test data (which works). {Yeah, I know… I’ll dump jQ, but it was easy to test ajax to make sure it works in the first place!}. Anyway, when the ons-input loses focus, ajax occurs, which gets a reply, and ons.notification.alert() is called. If I hit the Android’s back button while this notification is up, the app exists. I would expect that the notification would close, then if I hit the back button again, I would go to page one, then if I hit the back button again, the app would exit.

I tested this a little further, and on page one, I have another button, and in this button I have:

 onclick="ons.notification.alert('hello');"

While this message is up, if I hit the android back button, the app closes. This is unexpected behavior… I expect that the alert would close, not that the app would exit.

@Fran-Diox, Ok, I think I am slowly starting to get it, but just prepare to see my name pop up a lot for a while with lots of questions and scenarios… and I do appreciate your responses!

To clarify what you said in the second paragraph above, when you talk about putting the splitter as the parent of the navigator… more specifically, are you talking about the navigator being a child of ons-splitter-content?

<splitter>
    <splitter-side>
    </splitter-side>
    <splitter-content>
        <navigator></navigator>
    </splitter-content>
</splitter>

And on this topic of navigator, this is how I imagine it, so pease tell me if this makes sense and if it sounds right: I have a box (like a cardboard box, called the nagivator). In this box, I toss in a sheet of paper (pushPage(page1)). I can see page one and everything that is written on it. Then I toss in a second sheet of paper (pushPage(page2)). I can see the contents of that piece of paper. I obviously can’t see the contents of page1 anymore because page2 is covering it… but page1 still exists… but covered by page2… until page2 is popped. When page2 is popped (remove from the navigator box), I can see page1 again.

Assuming this is correct, I’ve a couple questions about this, because I’m having some trouble with some code of mine, and I think it deals with both navigators and templates. I have a pen here: https://codepen.io/mrphuzz/pen/zpbgNO. This pen behaves exactly as the app does when ran as an app on Android.

When page2 is popped, where does it go?

What I expect: I open the app (or the web app, again, both behave the same), and it shows “No items yet” on the “home” page. I click the FAB to add a new item, type in “Carrot,” and I click the Add Item button. The screen then goes back to the home page and it would show one item, “carrot.” I then click the menu button in the upper left and tap “Home.” The screen would reload the “home” page, showing the list that, in this case, only contains the single list item, “carrot.” I should then be able to click on the FAB or the “Add” menu, be taken to the Add page, and add a new item.

What happens: Everything is as expected until then end, when I open the menu and tap “Home.” In this case, instead of showing the single list item, “carrot,” it shows the three hard-coded filler items, “Filler-1,” “-2,” and “-3.” I can get to the add page again, but when I add a new item, just the filler list is visible, not the shopping list.

(I think writing this stuff is therapeutic and it helps me see things…)

<strikethrough>I am not sure what is happening. What I THINK is happening is that every time I tap the “Home” menu item, it creates a new page from the template and stacks it on top of my list, or, if I keep opening the menu and keep tapping Home, it keeps creating more and more “home” pages and throwing them on top of the last one. I think this because if I do this many times, then hit Android’s back button many times, I eventually see my shopping list… then when I hit back one more time, the app exits (as I would expect).</strikethrough>

Assuming my interpretation of what I see if correct (edit: it is), I’m not sure how to proceed. How can I prevent from duplicating the home page? When I tap the Home menu item, how do I access the home page that has my shopping list in it? Or, possibly, am I asking the wrong questions?

Edit: So I F12’d Chrome clicked the menu button many times, and it is as I deduced – multiple home pages. So… what do I do?

Thanks!

PS… I don’t know who’s in charge of this website, but the autogrowing textarea needs to have a maximum height… like the height of the preview, or let the bottom frame grow along with the textarea. I had to write this in notepad then copy/paste because the textarea went below the screen and I couldn’t see what I was typing.