fix(input, textarea): input does not block floating label - #27870
Merged
Conversation
liamdebeasi
marked this pull request as ready for review
July 27, 2023 13:51
liamdebeasi
requested review from
a team and
mapsandapps
and removed request for
a team
July 27, 2023 13:51
Contributor
Author
liamdebeasi
enabled auto-merge
July 27, 2023 14:22
sean-perkins
suggested changes
Jul 27, 2023
|
|
||
| If you need to add E2E tests that are only run on a specific version of the JS Framework, replicate the `VersionTest` component on each partial application. This ensures that tests for framework version X do not get run for framework version Y. | ||
|
|
||
| ### Testing Lazy Loaded Ionic Components |
Contributor
There was a problem hiding this comment.
This change should be reverted. It probably just got tracked between switching branches.
Contributor
Author
This reverts commit b4bad45.
mapsandapps
approved these changes
Jul 27, 2023
mapsandapps
left a comment
Contributor
There was a problem hiding this comment.
Looks good. I confirmed that the fix works (and I saw the bug submitter confirmed as well), and it looks like everything else works like before. 👍🏻
thetaPC
requested changes
Jul 27, 2023
| }); | ||
| }); | ||
| test.describe(title('input: floating/stacked label layering'), () => { | ||
| test('label should not be covered by text field', async ({ page }) => { |
Contributor
There was a problem hiding this comment.
Let's add a testInfo.annotations to track the reason behind this test.
| }); | ||
| }); | ||
| test.describe(title('textarea: floating/stacked label layering'), () => { | ||
| test('label should not be covered by text field', async ({ page }) => { |
Contributor
There was a problem hiding this comment.
Let's add a testInfo.annotations to track the reason behind this test.
sean-perkins
approved these changes
Aug 1, 2023
3 tasks
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
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.


Issue number: resolves #27812
What is the current behavior?
We currently have CSS to ensure the floating/stacked label is not obscured by the input/textarea when using the outline styles. However, it was discovered that this scenario can happen with any floating/stacked label not just when the input/textarea is using the outline style.
What is the new behavior?
Does this introduce a breaking change?
Other information
Dev build:
7.2.1-dev.11690464203.1b2b4419