New issue
Advanced search Search tips

Issue 837547 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 679237
Owner: ----
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression in CSS Transforms L2 scale() shorthand syntax

Reported by chris.ru...@gmail.com, Apr 27 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36

Steps to reproduce the problem:
1. Use shorthand syntax, single-value scale() according to CSS Transform L2.

.el {scale: 1.333;}

What is the expected behavior?
Element should scale in both X and Y axes, similar to pre-existing syntax using transform property. According to spec for scale shorthand:

> If only the X value is given, the Y value defaults to the same value.

https://drafts.csswg.org/css-transforms-2/#individual-transforms

What went wrong?
The element scales only in X axis, resulting in a distorted element.

Specifying two values in shorthand scale() produces expected outcome:

.el {scale: 1.333 1.333;}

Did this work before? Yes It worked as of Chrome 53, the first release with experimental support for shorthand syntax.

Does this work in other browsers? Yes

Chrome version: 65.0.3325.181  Channel: stable
OS Version: OS X 10.13.4
Flash Version: 

Bug was noticed on this how-to about the shorthand syntax. A couple other not-as-reduced tests can be found there: https://chrisruppel.com/blog/css-transforms-level2-translate-scale-rotate/
 
reduced-test_css-transforms-level2-scale-shorthand.html
1.8 KB View Download
css-transform-l2-scale-shorthand-bug.png
81.2 KB View Download

Comment 1 by woxxom@gmail.com, Apr 27 2018

Broken in 57.0.2977.0 by 55b9d2f5740a4e5f27b5c89a7503343f74cb8468
"CSS scale property: scale with one value only affects X"

Fixed in 66.0.3345.0 by f298c5e83c7ade370eb84522f01849643f050057
"CSS scale: Modified behaviour to match spec"

Current stable version of Chrome is 66 which has the bug fixed.
Whoops! I see now I needed a restart to get latest Stable. Sorry for the noise.

Comment 3 by cnardi@chromium.org, Apr 27 2018

Mergedinto: 679237
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment