Forum | Appery.io

But still, the problem is not that the event does not get fired. The problem is that the first time the list items shows, the second time it does not show because there is an attribute "display:none" added to the element. So the element from the page load is still there in the memory it just doesn't show anymore because of the display:none attirbute.

How and why does this happen? That's my question.

Hnto,

Yes, please send email to a href="mailto:support@appery.io" rel="nofollow"support@appery.io/a, but please make reference to this topic.

OK, sounds like your problem is very different from mine. In my case, I did want the event to fire, because the info in the DB could have changed.

Evgene, thanks for the clarification on the JQM.

I have sent you the link

Just a suggestion: can you put something in the Page Show event to reset the attribute, without actually doing the REST call? This may be a work-around for you, until Appery figures out why the display attribute is getting set to "none".

Good idea, thanks! Still a work around until it is fixed, but it works now.

There are just too many problems in this new builder. Almost all of my custom javascript does not work anymore.

• element.remove().children() does not work

• autodivider with alternate text does not work

• invoking page show with buttons adds NEW list items to the SAME listview. Now you have two new copies of the old list items.

• When I add code like this "element.append('');
  " it doesn't get added to the DOM strucute.

• My listitems are not clickable anymore if they are populated via rest and custom javascript code

  Everything described above was working fine in the old builder. I'm going back to the old builder and I'll wait till this is fixed.

  I know it's normal to change code when something is being upgraded. But this isn't changing the code because of the new builder, this is a bug and I'm not using the new builder until it's fixed.

Evgene, or any other Appery employee: could you please report these problems to the dev team? Because I'm pretty sure I'm not the only one having these problems.

I've debugged the app in the new builder and in the old builder and all the problems that I have described above are indeed bugs in the new builder.

For example: if you fire a page show event with a button, the rest service populates the DOM structure with NEW items instead of replacing it like it should do. In the old builder, the page show event would replace the old ones with the new ones. But the new builder just adds new items and leaves the old ones also. I've searched the Internet extensively and found out that the problem is probably due to the fact that 'deviceready' is being loaded twice.

And also the other problems: element.children().remove adds a display:none to the static list item AS WELL as the populated list items. What it should do is HIDE the static list item and show the populated items. As it did in the old builder.

• "element.append" does not get added to the DOM structure.

• list items are not clickable anymore if populated via rest service and custom javascript added.

  I would greatly appreciate it if you would forward this to the dev team, since I can't work in the new builder with my current projects if these bugs are still active. I can use the old builder, but you're gonna stop supporting that one and I want to be ready to use the new builder.

  In advance I thank you very much!

Hello Hnto!

May I ask you to share app with a href="mailto:support@appery.io" rel="nofollow"support@appery.io/a so we can attach your project backup to the bug report? Please let me know when it is shared.