[Form] Deprecate not configuring the default_protocol option of the UrlType
#50882
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2b543bd to
b99f459
Compare
… if they have skipped properties
|
Hi @MatTheCat, can you check your commit? it looks unrelated to this PR's proposal. |
|
Damn seems I’ve been mixing up my branches 😬 Opened #50922 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
You would expect an
<input type="url">from theUrlType, but it is not possible as long asdefault_protocolhas a value, because then you have to accept inputs that are not URLs (and you get an<input type="text" inputmode="url">).In order to change
default_protocolfrom'http'tonullin 7.0, we must first deprecate not configuring it.Don’t know how I can update tests though; all of
UrlTypeTest’s parent test cases will trigger the deprecation 🤔