I’m building an app in WeWeb where the visibility of elements is controlled by query strings in the URL.
For example:
my-url?edit=yes
In production, this works perfectly 
:
When I use the “Navigate to” action to go to the same page and change only the query parameters, the URL updates correctly and the elements controlled by these queries are displayed as expected.
However, in the WeWeb Editor, if I use Navigate to → same page and only change the queries (without changing the page), nothing happens.
It only works if:
-
I navigate to a different page, or
-
I change page parameters.
This behavior creates a real limitation during development, because it forces me to use workarounds just to test simple flows that depend on query parameters.
In practice, it makes it harder to build and preview dynamic apps in the Editor.
In short:
-
In production:
Navigate to (same page + query)→ works -
In the editor:
Navigate to (same page + query)→
nothing happens
It would be really helpful if the Editor could simulate the same behavior as production in this case, as it would make building and testing query-based dynamic components much easier.
Has anyone else run into this? 
