Closed Bug 13215 Opened 25 years ago Closed 24 years ago

child elements placed outside parent elements bounding rectangle are not erased when element is moved via javascript

Categories

(Core Graveyard :: GFX, defect, P3)

Product:
Core Graveyard
Component:
GFX
Platform:
x86
Windows 95
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 13213
Milestone:
Future

People

(Reporter: dan6992, Assigned: kmcclusk)

References

(
URL
)

Details

When an element has a child element that is placed outside it's bounding rectangle the child element is not erased properly when the parent element is moved via javascript. This causes the screen to be cluttered with trash, that can only be erased by minimizing the browser window.
Assignee: troy → beard
Component: Layout → Compositor
Patrick, this is a compositor issue. Child views are allowed to stick outside their parent view, and that means when the parent moves its child views that stick outside and are visible need repainting as well
Status: NEW → ASSIGNED
Target Milestone: M14
Wow, this also seems to affect view hit testing as well. A simple, is click in parent isn't good enough. If one of the little boxes is dragged outside the big box, they can no longer be dragged. Who knew?
Target Milestone: M14 → M15
Reassigning all compositor bugs to kevin.
Assignee: beard → kmcclusk
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
Bulk moving to M16
Target Milestone: M15 → M16
Moving to M17
Target Milestone: M16 → M17
Are this bug and Bug 13213 related? The trash only seems to come from things hanging from the top or left side of an object. Bug 13213 is a bug where child elements placed outside of their parent's top or left side do not register events properly. Should we make these two bugs dependant on each other?
Renders correctly with 5/17/2000 build on WINNT. However, after dragging the child elements outside the parent elements bounding box I can no longer click on the child element. I am marking this FIXED since the event problem is separate and covered by bug 13213
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
This is working in the May 22 nd build. Marking verified.
Status: RESOLVED → VERIFIED
This bug is back in the 7/24 build so I'm reopening it.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
This bug has been marked "future" because the original netscape engineer working on this is over-burdened. If you feel this is an error, that you or another known resource will be working on this bug,or if it blocks your work in some way -- please attach your concern to the bug for reconsideration.
Target Milestone: M17 → Future
This bug is effecting my work on the image map editor for Composer. The image map editor is written completely in javascript, with no native C++ code, so it is impossible for me to remedy this problem on my own (my C++ skills are very limited). I know it is not an extremely high priority, but it should be fixed before release.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 24 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 13213 ***
Verifying as a duplicate of bug 13213 '[EVENTTARG] events don't reach elements to top or left of view'
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.