When pressing 'back' - I get a completely unstyled basic page until I refresh again

Wappler General Bugs
1

======== TEMPLATE BUG FORM ========

Wappler Version : 3.4.1
Operating System : Mac
Project: NodeJS, MySql8, Docker.

Expected behavior

This happens in two scenarios:

  1. I click through to a page, pre-loader takes a while so I decide to click 'back' - this should take me to the previous screen without issues.
  2. I click through to Stripe checkout but then press back - and the same thing happens, I get the previous page in the app but it's completely unstyled.

This is definitely something the end-users will do.

Actual behavior

What actually happens?

Once I press back, I get a completely unstyled, basic 'html' like page. So I assume assets are not re-loading on 'back'. If I refresh the page, it goes back to normal.

1 Like
2

Sounds more like a local browser issue? Have you tried with a different browser just to eliminate that?

3

Why would this be a browser issue? What can I look into?

And yep, this is occurring to more than one of our team when testing - on completely different machines and browsers.

4

Was just throwing out ideas of what I would check next. I just can’t see how anything in Wappler would cause that. Hopefully the team has an idea to check.

1 Like
5

Thanks Brad and understood - sorry my questions were direct - I was just wondering how I would be able to check / debug if it’s a local browser issue.

It does seem strange, I imagine with the new templating system that the assets are just not being reloaded or there is a cache issue perhaps?!

6

@Teodor @patrick - can you help here? This happens consistently.

7

@Teodor - bump. Any advise here appreciated.

9

@patrick - @Teodor any updates here? About to go live and often if we press ‘back’ then we get this issue.

10

Is the back button working without preloader?

We have encountered some probles with Wappler reordering the js when preloader is implemented.

11

Hey @swf. Nope - this isn’t exclusive to the pre-loader unfortunately. We have this issue going back from a few different scenarios

12

Do you see some errors in the console of the browser devtools?

13

What kind of page was it, is it a SPA where the content was loaded using AJAX? Check the network tab to see what it tries to load and if there are any errors in the console. Do you perhaps have a link to the page where we can check the issue, or perhaps you could create a small video showing the exact issue.

14

Hey @patrick - we do use the internal linking, for speed but all pages are standalone, so I wouldn’t say it’s an SPA due to that.

Here is a short video: https://www.loom.com/share/5d03e93b67384cba8bf6bb306ed5a34e

I don’t see any errors in network tab, but I do see one small error relating to a stripe JS, but can’t see how this is affecting this, but I’ll look into that regardless:

Uncaught SyntaxError: Unexpected token '<'

15

We saw this related to href links. If we used href rather than DMX Browser a similar thing occurred a few weeks back… Are you linking directly to pages using href anchors? If so try replacing with a DMX Browser Goto action instead. May narrow it down?

16

Thanks Dave, these are all internal links - noting though it does happen if we link externally and then go back. Seems to happen in quite a few scenarios

17

Try temporarily replacing with the DMX Browser links see if that rectifies it? Worth a shot.

18

With standalone pages I have never seen it happen, looks like it stopped parsing the html (perhaps related to the SyntaxError) and the css is not applied. Also at the end of the movie I see some unrendered app connect expressions, so also JavaScript wasn’t executed there.

19

Ok…so what do you think I can do here? Is there something I’ve done wrong?

1 Like
20

I am experiencing the same problem with my Node SPA on chrome, safari and firefox.