Changes for PayPal affect core config fields with tooltip

[AndreasMueller75]

Preconditions (*)

1. Magento 2.3.1
2. PHP 7.*

Steps to reproduce (*)

1. create an config field, type time with a tooltip in a group in a section (see below)

<?xml version="1.0" ?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Config:etc/system_file.xsd">
    <system>
        <section id="shipping" showInDefault="1" showInStore="1" showInWebsite="1" translate="label tooltip comment">
            <group id="test_group" showInDefault="1" showInStore="1" showInWebsite="1" sortOrder="0" translate="label tooltip comment">
                <field id="test_time" showInDefault="1" showInWebsite="1" showInStore="0" sortOrder="10"
                       translate="label tooltip comment" type="time">
                   <label><![CDATA[Test Time]]></label>
                   <source_model>Magento\Config\Model\Config\Source\Date\Short</source_model>
                   <tooltip><![CDATA[Testtooltip.]]></tooltip>
                </field>
            </group>
        </section>
    </system>
</config>

Expected result (*)

The time fields are separated by colons (:)

Actual result (*)

The colons are missing (have a font-size of 0).

The reason

The change in vendor/magento/theme-adminhtml-backend/Magento_Backend/web/css/source/module/main/_collapsible-blocks.less from the following commit sets the font-size of all input-field labels with a tooltip to 0.

 .value {
            padding-right: 40px;
            vertical-align: middle;
            width: 44%;

            &.with-tooltip {
                font-size: 0;

Proposed Resolution

The css selector (.accordion .config .value.with-tooltip) is too general and should be more precise for setting font-size: 0 in PayPals usecase.

[magento-engcom-team]

Hi @AndreasMueller75. 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-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

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

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

• yes
• no

[AndreasMueller75]

Hi, i reworked the issue description. The issue is easily reproducible in Magento 2.3.1.

[magento-engcom-team]

✅ Confirmed by @engcom-backlog-nazar
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-98971 were created

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

[geet07]

I am working on this at #dmcdindia19”

[magento-engcom-team]

@geet07 thank you for joining. Please accept team invitation here and self-assign the issue.

[m2-assistant]

Hi @geet07. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

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

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

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

• 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[magento-engcom-team]

Hi @AndreasMueller75. Thank you for your report.
The issue has been fixed in #23393 by @geet07 in 2.3-develop branch
Related commit(s):

• eb28f14cc4a1d8b5c3d5ac5bff037a3b5661b833

The fix will be available with the upcoming 2.3.3 release.