Bug 110550

Summary:

font size in relative units not handled correctly in canvas contexts

Product:

WebKit

Reporter:

John Daggett <jdaggett>

Component:

Canvas

Assignee:

Nobody <webkit-unassigned>

Status:

NEW

Severity:

Normal

CC:

bdakin, bfulgham, dino, mitz, simon.fraser, webkit-bug-importer

Priority:

Keywords:

InRadar

Version:

528+ (Nightly build)

Hardware:

Unspecified

OS:

Unspecified

URL:

http://people.mozilla.org/~jdaggett/tests/cascade-canvastext.html

Attachments:

Description	Flags
screenshot, testcase in Webkit Nightly	none
Test Case	none
Expected Output (Chrome)	none

John Daggett

Reported 2013-02-21 21:01:05 PST

Created attachment 189673 [details] screenshot, testcase in Webkit Nightly Webkit does not appear to be following the spec when parsing font property values in canvas contexts. Steps: - Open URL Expected Result: all 8 tests should render identically, only the color should vary Result: altering the font-size of the canvas elements or other elements in the parent chain does not affect relative font sizes as expected. Note: in Safari 6.0.2 the testcase displays corrupted text but Webkit nightly/Chrome dev both show the text but at incorrect size. Tested in Webkit Nightly r143614, Chrome 26.0.1410.10 dev (OSX 10.8.2, Retina MacBook Pro)

Attachments
screenshot, testcase in Webkit Nightly (99.62 KB, image/png) 2013-02-21 21:01 PST, John Daggett	no flags	Details
Test Case (5.12 KB, text/html) 2022-07-18 15:09 PDT, Brent Fulgham	no flags	Details
Expected Output (Chrome) (510.88 KB, image/png) 2022-07-18 15:10 PDT, Brent Fulgham	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Brent Fulgham

Comment 1 2022-07-18 15:09:31 PDT

Created attachment 460988 [details] Test Case

Brent Fulgham

Comment 2 2022-07-18 15:09:51 PDT

This is still an issue in Safari 16.

Radar WebKit Bug Importer

Comment 3 2022-07-18 15:10:08 PDT

<rdar://problem/97222477>

Brent Fulgham

Comment 4 2022-07-18 15:10:52 PDT

Created attachment 460989 [details] Expected Output (Chrome)

Note You need to log in before you can comment on or make changes to this bug.