I’m struggling a bit with the target attribute. it works pretty good with ‘_top’, but according to the docs, when I want to affect a turbo-frame context ‘b’ from within a turbo-frame context ‘a’ I should use the target=‘b’ option.
By default, navigation within a frame will target just that frame. This is true for both following links and submitting forms. But navigation can drive the entire page instead of the enclosing frame by setting the target to
_top . Or it can drive another named frame by setting the target to the ID of that frame.
It turns out that it’s not working at all, I’m using something like that:
<turbo-frame id='a' target='b'> <!-- some action --> </turbo-frame> <turbo-frame id='b'> <!-- result --> </turbo-frame>
Also, my response do have the turbo-frame context b.
Have you guys faced this behavior as well ?.