Opened 13 years ago
Closed 12 years ago
#3144 closed defect (fixed)
VML's image may behave incorrectly when used alone in a picture
| Reported by: | Eugene Lazutkin | Owned by: | Eugene Lazutkin |
|---|---|---|---|
| Priority: | high | Milestone: | 0.9 |
| Component: | DojoX GFX | Version: | 0.9 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description
Sometimes VML's image "picks up" transformation matrix of other elements. See attached test case.
Attachments (1)
Change History (9)
Changed 13 years ago by
| Attachment: | test_image_bug.html added |
|---|
comment:1 Changed 13 years ago by
| Status: | new → assigned |
|---|
comment:2 Changed 13 years ago by
| Milestone: | 0.9beta → 0.9 |
|---|
comment:3 Changed 13 years ago by
| Summary: | VML's image may behave incorrectly while used alone in a picture → VML's image may behave incorrectly when used alone in a picture |
|---|
comment:4 Changed 12 years ago by
| Milestone: | 0.9 → 1.0 |
|---|
comment:5 Changed 12 years ago by
| Milestone: | 1.0 → 0.9 |
|---|
comment:6 Changed 12 years ago by
| Component: | gfx (svg+vml) → DojoX GFX |
|---|
comment:7 Changed 12 years ago by
Apparently the VML group has a notion of the origin, which is the minimal coordinate on both axis. It has two repercussions:
- If we move the left-most top-most object, the image shape will be moved as well because the origin is changed now.
- If we move an object in the negative direction (beyond 0), the whole picture will move in the positive direction to compensate for the changed origin.
One way to get rid of #1 is to abandon VML groups completely and support them only on virtual level. We do it now, but this is one step beyond that.
I have no ideas on how to fix #2. :-(
comment:8 Changed 12 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
This defect is subtle, and doesn't change the API --- I am retargeting it to 0.9.