ugh, it didn't save my html changes
but the decorator works if the template is set up with
<span as-foo>{{bar}}</span><input value="{{bar}}" />
huh
it also missed the duration passed to animate
I've always used .html but I'm it'll be easier to get syntax highlighting of the handlebars if I start using a different extension
Also VS Code does some weird formatting of handlebars
I have one main component and a few child components
based on different situations some child components get visible or invisible
when they get visible, they'll have some data rendered from an API call result.
There are situation where when one of child component is get's invisible others need to be visible
What's the best strategy for achiving this?
Imange it's an edit form when I save the form should be invisible and a previous component should get visible
So I'm trying to use component scoped css in Ractive and it seems to work as expected when I throw my css in the
css initialization prop in my component. But If I put a <style> tag in the component template instead, it just throws it into a style tag unmodified in the <body>. This bit of the docs seems to imply that component scoped css is supported if I put my css in the component template. https://ractive.js.org/api/#component-files
Am I wrong on that?
I wanted to put it in the template to get css syntax highlighting...
dang
Then when whatever happens that should trigger the reset, you could
on-click="doWhatever(), @.add('@shared.mydecoratortrigger')"
you could also do a similar thing with a feww ractive instance that the decorate module initializes and uses as an event bus
I'm having issues where a
stopPropagation call is seemingly not working as expected when I call it in a section. But I'm still trying to narrow it down.
you can hit them directly in the event handler on the element with something like
on-click="@.doSomething(), @event.stopImmediatePropagation()"
stop immediate will stop processing all ractive handlers as well
it's still not quite the same as a non-delegated event, because for certain event reasons, delegates always use capture, so if you have captures in the middle that are not handled by ractive, you will see things fire a little out of order