Activity

1. mordae

   changed the title [-]Support `up.reload(":none")`[/-] [+]Please support `up.reload(":none")`[/+] on Nov 29, 2023
2. triskweline commented on Nov 29, 2023

   

   triskweline

   on Nov 29, 2023

   Contributor

   More actions

   When reloading Unpoly needs an element to discover which URL to reload from, and which ETags / Last-Modified headers to send.

   👍React with 👍1Reacted by Jan Hamal Dvořák
3. mordae commented on Dec 7, 2023

   

   mordae

   on Dec 7, 2023

   Last edited by mordae

   ContributorAuthor

   More actions

   Ah, I see. Would it be possible to support the behavior described above as an option then? For example by making it possible to pass update targets that further restrict what children of the target element are actually replaced?
4. yaroslav-gwit commented on Jan 17, 2024

   

   yaroslav-gwit

   on Jan 17, 2024

   Last edited by yaroslav-gwit

   More actions

   I worked around a similar issue another way. I've created a JS function that was listening for a particular event (path change in my case, but it can be anything really), and once the event was triggered a block of code below had to update few elements (at once) on the page:

   // vmName variable was set above this block, to make an element that has to be updated more dynamic
   if (document.location.pathname.includes('/hosts/')) {
       up.render(`#vmActionButtons, .unpoly-snapshot-list`, { url: document.location.pathname });
   } else {
       up.render(`#vmActionButtons, #sidebarVm${vmName}, .unpoly-snapshot-list`, { url: document.location.pathname });
   }

   I hope this helps, or at least gives you some new ideas :)

   👀React with 👀1Reacted by Ricardo Sawir