Image is rotated differently in Chrome and Firefox
Categories
(Core :: Layout: Images, Video, and HTML Frames, defect)
Tracking
()
People
(Reporter: twisniewski, Assigned: dlrobertson)
References
(Regression, )
Details
(Keywords: regression)
Attachments
(2 files)
In the attached test-case, the JPEG image has a particular combination of crossorigin=anonymous, transform:rotate(90deg), and image-orientation:none. Something about this combination seems to cause Chrome to rotate it -90 degrees again despite the transform, while Firefox does not do so.
Dropping the crossorigin attribute causes Chrome to not rotate the image -90 degrees again, but I'm not well versed in whether or how these attributes are supposed to interplay, so I thought a second opinion would be good here.
| Reporter | ||
Updated•2 years ago
|
Comment 1•2 years ago
|
||
The severity field is not set for this bug.
:emilio, could you have a look please?
For more information, please visit auto_nag documentation.
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 2•2 years ago
|
||
The fix for this should be easy. To match the behavior of blink and webkit we need to use imgIRequest::GetCORSMode to get the request's cors mode and add logic to this check to ensure we do not take that branch that ignores image-orientation: none in the case that imgIRequest::GetCORSMode returned CORS_ANONYMOUS.
That being said, it is unclear to me currently if this is the expected or correct behavior. Based on the discussion in w3c/csswg-drafts#5165, I'd think we'd want to ignore image-orientation: none regardless of crossorigin="anonymous".
Comment 3•2 years ago
|
||
Set release status flags based on info from the regressing bug 1655598
Updated•2 years ago
|
Updated•2 years ago
|
| Assignee | ||
Comment 4•2 years ago
|
||
The image-orientation: none property should apply to images with
crossorigin="anonymous".
Comment 5•2 years ago
|
||
Set release status flags based on info from the regressing bug 1655598
Updated•2 years ago
|
Comment 8•2 years ago
|
||
| bugherder | ||
Comment 10•2 years ago
|
||
The patch landed in nightly and beta is affected.
:dlrobertson, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox113towontfix.
For more information, please visit auto_nag documentation.
| Assignee | ||
Comment 11•2 years ago
|
||
IMO not important enough for a uplift.
Updated•2 years ago
|
Reproducible on a 2023-04-10 Nightly build on Windows 10.
Verified as fixed on Firefox 114.0b2(build ID: 20230509180058) and Nightly 115.0a1(build ID: 20230509215006) on Windows 10, macOS 12, Ubuntu 22.
Description
•