Closed
Bug 836325
Opened 11 years ago
Closed 1 year ago
seam between images when using a scale transform
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
WORKSFORME
mozilla29
People
(Reporter: tagliapietra.alessandro, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(5 files, 2 obsolete files)
At work we're developing a zoomable image viewer, so we use a lot the transform functions. On firefox I've seen that when the parent of two or more images has a scale3D different then 0 there is a space between the images contained inside it. The issue seems to be on just one image every two, seems like a sub pixel shifting that makes one image overlap the other and the other has space between the next one. I'll attach a test html and two images to test this.
Reporter | ||
Comment 1•11 years ago
|
||
Reporter | ||
Comment 2•11 years ago
|
||
Reporter | ||
Comment 3•11 years ago
|
||
Attachment #708145 -
Attachment is obsolete: true
Updated•11 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Reporter | ||
Comment 7•11 years ago
|
||
Someone can work on this?
Updated•11 years ago
|
Flags: needinfo?(tnikkel)
Comment 8•11 years ago
|
||
Layout does pixel snap these images, but we end up drawing them with antialiased edges (which can be easily seen by drawing just one image), so somewhere along the line that doesn't quite happen. And I haven't had time to dig into this further to determine exactly what is going on.
Summary: Wrong positioning of children elements when parent has scale3D transforms → seam between images when using a scale transform
Comment 9•11 years ago
|
||
This testcase is a bit simpler.
Probably because our cairo-quartz backend doesn't support EXTEND_CLAMP properly?
Comment 11•11 years ago
|
||
It happens on Linux and Windows too.
Comment 12•11 years ago
|
||
I'm probably not going to get to this soon. Clearing needinfo so the big red dot goes away and stops bugging me.
Updated•11 years ago
|
Flags: needinfo?(tnikkel)
Comment 13•10 years ago
|
||
Looks like this was fixed by bug 948848.
Status: NEW → RESOLVED
Closed: 10 years ago
Depends on: 948848
Resolution: --- → FIXED
Target Milestone: --- → mozilla29
Comment 14•10 years ago
|
||
Alessandro, could you please verify that this issue is fixed for you in Firefox 29?
Flags: needinfo?(tagliapietra.alessandro)
Whiteboard: [good first verify]
Reporter | ||
Comment 15•10 years ago
|
||
Non working screenshot with version 30.0a1 (2014-03-10)
Reporter | ||
Comment 16•10 years ago
|
||
I've uploaded the screenshot I get with version 30.0a1 (2014-03-10), where can I download version 29 to test? Since the beta channel has the 28 at the moment.
Status: RESOLVED → REOPENED
Flags: needinfo?(tagliapietra.alessandro)
Resolution: FIXED → ---
Comment 17•10 years ago
|
||
I can confirm that this is not fixed on nightly anymore, so I'm guessing it must have been re-regressed. It is however still fixed for me on Aurora. We should find out what regressed this since comment 13.
Keywords: regressionwindow-wanted
Whiteboard: [good first verify]
Comment 18•10 years ago
|
||
Hmm, works fine on linux. Might the new regression be mac specific?
Comment 19•10 years ago
|
||
(In reply to Cork from comment #18) > Hmm, works fine on linux. Might the new regression be mac specific? It could be.
Comment 20•10 years ago
|
||
New regression range http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=4cb766685b73&tochange=529b86b92b1d
Comment 21•10 years ago
|
||
Most likely http://hg.mozilla.org/mozilla-central/rev/3637434788e5 (bug 976877)
Blocks: 976877
Keywords: regressionwindow-wanted
Updated•2 years ago
|
Severity: normal → S3
Updated•1 year ago
|
Comment 22•1 year ago
|
||
Unable to reproduce in recent versions.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 1 year ago
Resolution: --- → WORKSFORME
Updated•1 year ago
|
Keywords: regression
You need to log in
before you can comment on or make changes to this bug.
Description
•