Closed Bug 1236459 Opened 9 years ago Closed 5 years ago

Bug in DOMMatrix calculations.

Categories

(Core :: DOM: CSS Object Model, defect)

Product:
Core
Component:
DOM: CSS Object Model
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: trusktr, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36 Steps to reproduce: 1. Make a new DOMMatrix. 2. Call rotate() on it and look at the value of m11 of the returned matrix: 0.7071067811865475 3. Call rotateSelf() on the original matrix then look at m11 on it, which appears to be wrong: 0.7071067690849304 Actual results: A calculation error (caused by casting?). Expected results: Both calculations should have the same result, but they don't. Original w3c mailing list thread: https://lists.w3.org/Archives/Public/public-fx/2016JanMar/0003.html
Component: Untriaged → DOM: Core & HTML
Product: Firefox → Core
This seems close enough that it's fall under the hardware limitations clause. OTOH, we might want to be more accurate for this API in particular.
Component: DOM: Core & HTML → DOM: CSS Object Model

I can't reproduce this now, can you?

Flags: needinfo?(trusktr)
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
Flags: needinfo?(trusktr)
You need to log in before you can comment on or make changes to this bug.