Avoid postcss-px-to-rem transform px failback

Created on 13 March 2024, 9 months ago
Updated 29 March 2024, 9 months ago

Problem/Motivation

in css reset ticket we got failback `--admin-toolbar-rem` but seems css wasn't generated well there. So now in 1.x `yarn build` command transform variables to --admin-toolbar-rem: max(1rem, 1rem); what is incorrect in terms of that failback.

Proposed resolution

set --admin-toolbar-rem: max(1rem, 16PX);
to avoid its transformation

https://www.npmjs.com/package/postcss-pxtorem#a-message-about-ignoring-p...

šŸ› Bug report
Status

Fixed

Version

1.0

Component

Code

Created by

šŸ‡·šŸ‡øSerbia finnsky

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @finnsky
  • Status changed to Needs review 9 months ago
  • Merge request !196Avoid px transformation - #3427520 ā†’ (Merged) created by finnsky
  • Pipeline finished with Success
    9 months ago
    #117957
  • šŸ‡ŖšŸ‡øSpain ckrina Barcelona

    Commenting here also what I've mentioned in Slack for the record: Iā€™m actually wondering if we should really be using postcss-px-to-rem and just write the code with the unit it needs and get rid or auto-conversions. IMHO our code is small enough to control that.

  • šŸ‡·šŸ‡øSerbia finnsky

    @ckrina i think we need to merge this small fix,
    because `yarn build` now always generate that 1rem-1rem :)

    And probably reopen discussion ticket

  • šŸ‡·šŸ‡øSerbia finnsky

    @rishabjasrotia
    Why extra patch needed here?

  • Pipeline finished with Success
    9 months ago
    Total: 151s
    #119846
  • Pipeline finished with Success
    9 months ago
    Total: 144s
    #119852
  • Status changed to Fixed 9 months ago
  • šŸ‡ŖšŸ‡øSpain ckrina Barcelona

    Fixed, thanks @finnsky! I've also added a comment next to it so it's obvious why it's there and opened šŸ“Œ Remove postcss-px-to-rem from Navigation Active .

    @rishabjasrotia thank you for your interest in working on this issue.
    This issue works with a merge request (MR), so posting additional patches (especially with the same code) is not helpful. In general, patches should be avoided from now on.
    In the future, you can get credit for issues by reading the issue to understand its purpose, and taking into account all the discussion on the issue. More information on the issue credit guidelines ā†’ . Thanks!

  • Hello @finnsky it is the same code patch added until issue was not merged to be used.

  • Automatically closed - issue fixed for 2 weeks with no activity.

  • Pipeline finished with Canceled
    5 months ago
    #246790
  • Pipeline finished with Success
    5 months ago
    #246793
  • Pipeline finished with Success
    5 months ago
    #246818
  • Pipeline finished with Success
    5 months ago
    #246827
  • Pipeline finished with Success
    4 months ago
    Total: 262s
    #261626
  • Pipeline finished with Canceled
    3 months ago
    Total: 75s
    #279211
  • Pipeline finished with Canceled
    3 months ago
    Total: 74s
    #279212
  • Pipeline finished with Success
    3 months ago
    Total: 378s
    #279220
  • Pipeline finished with Canceled
    3 months ago
    Total: 85s
    #279593
  • Pipeline finished with Success
    3 months ago
    Total: 534s
    #279594
  • Pipeline finished with Success
    3 months ago
    Total: 384s
    #279614
  • Pipeline finished with Success
    3 months ago
    #279645
  • Pipeline finished with Failed
    3 months ago
    Total: 1152s
    #280226
  • Pipeline finished with Failed
    3 months ago
    Total: 958s
    #280398
  • Pipeline finished with Success
    3 months ago
    Total: 1235s
    #280416
Production build 0.71.5 2024