Side navigation
#8123 closed bug (fixed)
Opened February 01, 2011 01:45PM UTC
Closed February 01, 2011 01:57PM UTC
Last modified March 09, 2012 11:53AM UTC
.clone() defaults to cloning events in 1.5
Reported by: | scottgonzalez | Owned by: | john |
---|---|---|---|
Priority: | blocker | Milestone: | 1.5.1 |
Component: | event | Version: | 1.5 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
The default behavior of .clone() is not supposed to copy events, but as of 1.5 it does.
Attachments (0)
Change History (12)
Changed February 01, 2011 01:49PM UTC by comment:1
component: | unfiled → event |
---|---|
milestone: | 1.next → 1.5.1 |
owner: | → john |
priority: | undecided → blocker |
status: | new → assigned |
Changed February 01, 2011 01:50PM UTC by comment:2
Changed February 01, 2011 01:57PM UTC by comment:3
resolution: | → fixed |
---|---|
status: | assigned → closed |
The default for .clone() is to not clone any events. Fixes #8123.
Changeset: 375b78783825b9adab7a01541faf99f98ef7ecbd
Changed February 11, 2011 03:05AM UTC by comment:9
with the patch, the default behavior for deepWithDataAndEvents is changing from false to whatever WithDataAndEvents is. Is that correct and intended?
Changed February 11, 2011 03:06AM UTC by comment:10
Yes, correct and intended
Changed February 17, 2011 09:21AM UTC by comment:11
#8299 is a duplicate of this ticket.
Changed September 07, 2011 12:10PM UTC by comment:12
#10212 is a duplicate of this ticket.