Missaligned fields on the Customer Login form

[gjportegies]

Preconditions (*)

1. Magento CE 2.3.5-p1 vanilla without sample data is installed.
2. Magento Blank Theme is used.
3. Screen/Browser width >= 768px.

Steps to reproduce (*)

1. Login to the admin panel.
2. Navigate to the Content -> Design -> Configuration.
3. Open the Global Store and set the applied theme to 'Magento Blank'.
4. Clean the cache(s).
5. Open the storefront and navigate to the 'Sign In' page (/customer/account/login/)
6. See the input fields on the Customer Login form are not stroking with the design of all other forms on the default Blank Theme.

Expected result (*)

The input fields on the form should be inline with the labels (Like all other forms in the Blank Theme).

Expected Result

Actual result (*)

The input fields are shown below the labels and not aligned.

Actual Result

Additional information

On the Magento 2.4-develop instance the issue looks fixed. But this is not stroking with the styling of all the other form fields design of the Magento Blank theme.

Result on 2.4-develop

On the Magento 2.3.5-p1 the issue is probably caused by the following css line:

[m2-assistant]

Hi @gjportegies. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@gjportegies do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @krishprakash. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[krishprakash]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @krishprakash. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @krishprakash, here is your Magento instance.
Admin access: https://i-28059-2-4-develop.instances.magento-community.engineering/admin_dbce
Login: 053601f6 Password: 5c9703584465
Instance will be terminated in up to 3 hours.

[magento-engcom-team]

✅ Confirmed by @krishprakash
Thank you for verifying the issue. Based on the provided information internal tickets MC-33937 were created

Issue Available: @krishprakash, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[sdzhepa]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @sdzhepa. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @sdzhepa, here is your Magento instance.
Admin access: https://i-28059-2-4-develop.instances.magento-community.engineering/admin_b143
Login: b508383e Password: 0338fa230159
Instance will be terminated in up to 3 hours.

[sdzhepa]

Hello @mrtuvn
fyi: @krishprakash

I cannot reproduce this issue using steps from precondition on the latest 2.4-develop branch
Probably it was already fixed and we can close this issue
or some steps/preconditions are missed

Luma: 768x1024 and 1024x768

Blank: 768x1024 and 1024x768

UPDATE:
It seems I missed part expected results and additional information.
Lets summarise:

1. On the latest code of 2.4-develop we do not have like "shifted" titles. Titles are under input.
2. But the only issue is general styling for the Blank Theme.

• in the Luma theme, all titles are placed UNDER the input fields
• in the Blank theme, all titles are placed on the LEFT side of input fields
  

[gjportegies]

@sdzhepa did you read my comment on the additional information?

On the Magento 2.4-develop instance the issue looks fixed. But this is not stroking with the styling of all the other form fields design of the Magento Blank theme.

[slavvka]

Hi @gjportegies. Thank you for your report.
The issue has been fixed in #28084 by @mrtuvn in 2.4-develop branch
Related commit(s):

• d7cf1881141fd855ff79f611a31ea2570726bdc3
• 77a4e8c44e1ee901d77aa8d6680fcd5365cd376d
• 6b8fc4c55272229164fde82ddbd631f771f302d7
• facbe37f9f51eb315bc5da1fb3c5000d743057ff
• 1ef8a517089ff132a7bb526194999ae83247ce50
• 6e8190662497a8e248c05d92b8763886637be5f3
• 03a2908769ad60c5cd5b1a5262aeab092417fe6a
• 8c0eff01d09dbea47a3af3afbd0f75bae2a89c82
• 0e84ed4214d5a7bafdabf99dcaa45e2f54bdac41
• 63550be4ba9097cb1ceac4cc787632d330ec0ea1
• e3975c6b6461c0b1e1bce318cae04f4622f17bd7
• d68fa5d45b66754801e65b440d1338463396ad9f
• 63552f8538347bb4c21339be0100f6bda72c9d60
• 80c6ba7ec4ea21ef19bde70edb2477a5717a84cb

The fix will be available with the upcoming 2.4.0 release.