Skip to content

Logo is always 170 pixels wide, regardless of actual size #29721

Closed
@gwharton

Description

@gwharton

Preconditions (*)

  1. 2.4-develop

Steps to reproduce (*)

  1. Login to Admin
  2. Content -> Configuration -> Global -> Edit -> Header
  3. Upload 800x300 example logo image (attached to issue)
  4. Enter 800 in Logo Attribute Width
  5. Enter 300 in Logo Attribute Height
  6. Save Configuration
  7. Clear cache
  8. Go to frontend and inspect logo dimensions

Expected result (*)

  1. Logo is 800 pixels wide

Actual result (*)

  1. Logo is 170 pixels wide

image


Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

The cause is this

<page xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:View/Layout/etc/page_configuration.xsd">
<body>
<referenceBlock name="logo">
<arguments>
<argument name="logo_width" xsi:type="number">170</argument>
</arguments>
</referenceBlock>
</body>
</page>

And was introduced here. #27497

800x300 example logo

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area: FrontendComponent: ImageIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedIssue: Format is validGate 1 Passed. Automatic verification of issue format passedIssue: Ready for WorkGate 4. Acknowledged. Issue is added to backlog and ready for developmentPriority: P3May be fixed according to the position in the backlog.Progress: doneReported on 2.4.0Indicates original Magento version for the Issue report.Reproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branchSeverity: S3Affects non-critical data or functionality and does not force users to employ a workaround.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions