New issue
Advanced search Search tips

Issue 889277 link

Starred by 5 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

CSS Font-properties parsing issues

Reported by iecom...@gmail.com, Sep 25

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Edge/18.17763

Steps to reproduce the problem:
1. serialize the computed style of a font-style with angle in radians

What is the expected behavior?
Get the correct value in degrees

What went wrong?
Get the rounded radiant value reported as being degrees

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 64.0.3282.140  Channel: n/a
OS Version: 10.0
Flash Version:
 
testcase.font-style.angle.html
579 bytes View Download
NOTE: the attached file is a web platform testcase, but you can simply inspect the `getComputedStyle(document.body).fontStyle` in the console to see the problem.
Labels: Needs-Milestone
Cc: ajha@chromium.org
Labels: Target-71 M-71 FoundIn-71 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on the latest canary(71.0.3561.0) and stable(69.0.3497.100) on Windows-10, Mac OS 10.13.6 and Linux Debian rodete. Older chrome versions show as 'Normal' when inspecting 'getComputedStyle(document.body).fontStyle' in the console.

Triaging this as non-regression issue for more inputs on this.

Note: FF shows oblique 45deg and Chrome shows oblique 0.75deg.
Cc: drott@chromium.org futhark@chromium.org
Components: -Blink>Fonts Blink>CSS
Labels: -Pri-2 Pri-3
Status: Available (was: Untriaged)
It looks like we are passing degree values into FontDescription regardless of the unit of the parsed value.

Cc: andruud@chromium.org

Sign in to add a comment