Closed
Bug 759036
Opened 14 years ago
Closed 14 years ago
[Azure] Enabling Azure-Thebes breaks mask layers
Categories
(Core :: Graphics: Layers, defect)
Tracking
()
RESOLVED
FIXED
mozilla16
People
(Reporter: nrc, Assigned: nrc)
Details
Attachments
(4 files, 5 obsolete files)
|
637 bytes,
text/html
|
Details | |
|
301 bytes,
text/html
|
Details | |
|
4.58 KB,
patch
|
bas.schouten
:
review+
akeybl
:
approval-mozilla-aurora+
|
Details | Diff | Splinter Review |
|
8.24 KB,
patch
|
nrc
:
review+
akeybl
:
approval-mozilla-aurora+
|
Details | Diff | Splinter Review |
Bug 715768 (or possibly bug 757329) breaks masking of rounded rects for some cases. See the test case, with Accelerated layers enabled, DX10, when you mouse over the div, it renders correctly (the active path), but when the layer is inactive, it renders incorrectly, the mask is incorrectly translated by some amount.
I bisected m-c to identify those two changesets as the culprits.
As well as fixing the bug, we need some more tests for rounded rect clipping, but I get kind of stuck as to how to do them because of the subtle active/inactive layers thing.
| Assignee | ||
Comment 1•14 years ago
|
||
Attachment #630068 -
Flags: review?(bas.schouten)
| Assignee | ||
Comment 2•14 years ago
|
||
Sorry these took so long, I didn't know direct2D didn't work on Try so thought my test wasn't working. I have a passing Try run from earlier, but lost it, but it doesn't matter because it wasn't using Direct2D anyway :-(
Attachment #630069 -
Flags: review?(bas.schouten)
| Assignee | ||
Comment 3•14 years ago
|
||
The patch does not fix this new test case. Here there is a pattern, rather than a source surface in gfxContext, and the pattern transform is different to the draw target transform, the effect is that the image is painted into the wrong place, see the distortion on the rhs of the image. It needs both a scale and translate on the image, it looks like the scale and translate are applied in the wrong order, but I suspect that is not the problem, more likely the source and target transforms are being confused again. Other than that, I can't figure out what is causing this. It is fixed by turning off content Azure.
Comment 4•14 years ago
|
||
(In reply to Nick Cameron [:nrc] from comment #3)
> Created attachment 630098 [details]
> another test case
>
> The patch does not fix this new test case. Here there is a pattern, rather
> than a source surface in gfxContext, and the pattern transform is different
> to the draw target transform, the effect is that the image is painted into
> the wrong place, see the distortion on the rhs of the image. It needs both a
> scale and translate on the image, it looks like the scale and translate are
> applied in the wrong order, but I suspect that is not the problem, more
> likely the source and target transforms are being confused again. Other than
> that, I can't figure out what is causing this. It is fixed by turning off
> content Azure.
Try fiddling with the order anyway, I think that actually might be the cause!
| Assignee | ||
Comment 5•14 years ago
|
||
Assignee: nobody → ncameron
Attachment #630068 -
Attachment is obsolete: true
Attachment #630068 -
Flags: review?(bas.schouten)
Attachment #631119 -
Flags: review?(bas.schouten)
| Assignee | ||
Comment 6•14 years ago
|
||
Attachment #630069 -
Attachment is obsolete: true
Attachment #630069 -
Flags: review?(bas.schouten)
Attachment #631121 -
Flags: review?(bas.schouten)
Comment 7•14 years ago
|
||
Comment on attachment 631119 [details] [diff] [review]
patch
Review of attachment 631119 [details] [diff] [review]:
-----------------------------------------------------------------
This patch is against the patch I gave you, not against m-c. That's why you need to comment out several of the inverts :)
Comment 8•14 years ago
|
||
Comment on attachment 631121 [details] [diff] [review]
tests
Review of attachment 631121 [details] [diff] [review]:
-----------------------------------------------------------------
::: layout/reftests/bugs/759036-2-ref.html
@@ +2,5 @@
> +<html>
> +<head>
> +<style>
> +.clipround {
> + width:250px;
No tabs please! :)
::: layout/reftests/bugs/759036-2.html
@@ +2,5 @@
> +<html>
> +<head>
> +<style>
> +.clipround {
> + width:250px;
Here too
Attachment #631121 -
Flags: review?(bas.schouten) → review+
| Assignee | ||
Comment 9•14 years ago
|
||
Attachment #631119 -
Attachment is obsolete: true
Attachment #631119 -
Flags: review?(bas.schouten)
Attachment #631179 -
Flags: review?(bas.schouten)
| Assignee | ||
Comment 10•14 years ago
|
||
removed tabs (how did they get there?), carrying r=Bas
Attachment #631121 -
Attachment is obsolete: true
Attachment #631182 -
Flags: review+
Updated•14 years ago
|
Attachment #631179 -
Flags: review?(bas.schouten) → review+
| Assignee | ||
Comment 11•14 years ago
|
||
| Assignee | ||
Comment 12•14 years ago
|
||
Target Milestone: --- → mozilla16
Comment 13•14 years ago
|
||
Sorry, I had to back this out on inbound because of a reftest.list syntax error and a leak in debug reftests:
https://hg.mozilla.org/integration/mozilla-inbound/rev/253d5996845e
Target Milestone: mozilla16 → ---
| Assignee | ||
Comment 14•14 years ago
|
||
increased a fuzz slightly so it passes for non-Windows platforms. Carrying r=Bas
Attachment #631182 -
Attachment is obsolete: true
Attachment #632916 -
Flags: review+
| Assignee | ||
Comment 15•14 years ago
|
||
Target Milestone: --- → mozilla16
Comment 16•14 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/32586e976b50
https://hg.mozilla.org/mozilla-central/rev/537dc98ee4b4
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 17•14 years ago
|
||
Comment on attachment 631179 [details] [diff] [review]
patch
[Approval Request Comment]
Bug caused by (feature/regressing bug #): Bug 715768 (or possibly bug 757329)
User impact if declined: incorrect rendering of content with D2D and rounded corners
Testing completed (on m-c, etc.): yes
Risk to taking this patch (and alternatives if risky): no obvious risk
String or UUID changes made by this patch: none
Attachment #631179 -
Flags: approval-mozilla-aurora?
| Assignee | ||
Comment 18•14 years ago
|
||
Comment on attachment 632916 [details] [diff] [review]
tests
[Approval Request Comment]
see comment on patch approval request, these are the corresponding tests
Attachment #632916 -
Flags: approval-mozilla-aurora?
Comment 19•14 years ago
|
||
Comment on attachment 631179 [details] [diff] [review]
patch
[Triage Comment]
Definitely early enough in the cycle to take a regression fix like this. Approved for Aurora 15.
Attachment #631179 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Updated•14 years ago
|
Attachment #632916 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
https://hg.mozilla.org/releases/mozilla-aurora/rev/10d1a127d9b8
https://hg.mozilla.org/releases/mozilla-aurora/rev/ce812b5b6ab1
status-firefox15:
--- → fixed
tracking-firefox15:
--- → +
Comment 21•14 years ago
|
||
Backed out the reftest part from aurora, for failures:
https://tbpl.mozilla.org/?tree=Mozilla-Aurora&rev=ce812b5b6ab1
https://hg.mozilla.org/releases/mozilla-aurora/rev/42817f2f2c3e
(Is only the test part, but going to set back to affected, so this doesn't fall off the radar)
| Assignee | ||
Comment 22•14 years ago
|
||
status-firefox15:
affected → ---
tracking-firefox15:
+ → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•