Add test coverage for turbo-frame[disabled] #67
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Support for the
[disabled]
attribute pre-dates this commit, but islargely untested. Prior to hotwired/turbo-site#32 and
hotwired/turbo-site#36, there were no mentions of the attribute in
the Turbo Handbook or Reference documentation.
This commit adds functional test-level coverage for the existing
behavior. When an
<a>
or<form>
element targets a<turbo-frame disabled>
element, Turbo skips intercepting and intervening, andinstead navigates the page.
Testing
In addition, to avoid conflating
[data-turbo="false"]
and<turbo-frame disabled>
, this commit also renames test and test fixturementions of "disabled" to more accurately reflect which manner of
skipping behavior is being tested.