Page 1 of 1

Render all pages in one HTML file Master-Detail issue

Posted: Sat Dec 21, 2013 5:13 pm
by Matt

There seems to be a bug with switching between Master-Detail pages when using Render all pages in one HTML file. When loading a new master page, the left side content spacing and properties are not applied correctly to the components. The sizing is also incorrect. The only happens if you use Render all pages in one HTML file and selecting full page refresh on navigation has no effect either.

I have created a sample application at:
http://appery.io/app/view/25a47472-53...

If you click on the "test" button at the top, it will navigate to the second page and you will see the badly formatted content.

Please advise.

Thanks!
Matt


Render all pages in one HTML file Master-Detail issue

Posted: Sat Dec 21, 2013 7:48 pm
by Igor

Hello,

We'll test but it will take some time.


Render all pages in one HTML file Master-Detail issue

Posted: Mon Dec 23, 2013 1:58 pm
by Kateryna Grynko

Hi Matt,

We reproduced the issue, still working on it.


Render all pages in one HTML file Master-Detail issue

Posted: Tue Dec 24, 2013 3:34 pm
by Kateryna Grynko

Matt,

This is a bug, will be fixed.


Render all pages in one HTML file Master-Detail issue

Posted: Tue Jan 28, 2014 6:04 am
by Matt

Any status update on this issue?

Thaks!
Matt


Render all pages in one HTML file Master-Detail issue

Posted: Tue Jan 28, 2014 7:15 am
by Maryna Brodina

Hello! Sorry, still working on fix.


Render all pages in one HTML file Master-Detail issue

Posted: Tue Feb 04, 2014 1:50 am
by Matt

This bug is really holding up the deployment of our product. Any guess on a timeline or a workaround? Am I the only one having this issue?

Thanks!
-Matt


Render all pages in one HTML file Master-Detail issue

Posted: Tue Feb 04, 2014 11:56 am
by Maryna Brodina

Hello! It's planned for the next release in March, we're sorry for inconvenience.


Render all pages in one HTML file Master-Detail issue

Posted: Mon Apr 14, 2014 1:39 pm
by Maryna Brodina

Hello!

This bug was fixed.