temp stuff
Source codebubble example
Expected behavior: click a button and see its id displayedYou pressed:
You can set up the click behavior on the parent element and events will bubble up
disable pointer events on the parent and re-enable it on its children with CSS
referencebulk update
Expected behavior: background transition on activation/deactivationName | Status |
---|---|
John | Active |
check the inline style
load list items
Expected behavior: load 7 items maxItem 1
I think it is worth mentioning that you should not do validation with signals only, as they can be modified by the user
so... two solutions:
- track user state on the backend
- send a new button with a new route ("@get('/load_more/3')")
i went with the second approach, clears on page load but can handle navigation
redirect from the backend
Expected behavior: redirect, decrementing counter, history preservationredirecting with javascript script or logic inside an element is mostly a can of worms
we could slightly modify the docs to have a decrementing counter "d* style", like this