If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Copy/Paste a stack of events does not retain proper placement

VERIFIED FIXED

Status

Webmaker
Popcorn Maker
VERIFIED FIXED
4 years ago
4 years ago

People

(Reporter: Jacob, Assigned: mjschranz)

Tracking

Details

(URL)

Attachments

(3 attachments)

(Reporter)

Description

4 years ago
Created attachment 755034 [details]
stack of events being copied

I frequently need to copy and paste a stack of events that are layered on top of one another in the timeline. When I paste the stack, I expect it to be in the same shape, order, and placement as the stack that I copied, but this is never the case for me.

I'm attaching two screen shots, one showing the stack of events that I copied and one showing the pasted stack that occurs 3 layers up from where it's supposed to. (Luckily it's usually the same order, which used to not be the case).

Firefox 21.0 OS X 10.6.8
(Reporter)

Comment 1

4 years ago
Created attachment 755036 [details]
2nd screenshot of pasted stack occurring out of place
(Reporter)

Updated

4 years ago
Assignee: nobody → scott
(Assignee)

Updated

4 years ago
Assignee: scott → schranz.m
(Assignee)

Comment 2

4 years ago
Created attachment 773305 [details] [review]
https://github.com/mozilla/popcorn.webmaker.org/pull/105

First crack at this.
Attachment #773305 - Flags: review?(scott)
Attachment #773305 - Flags: review?(scott) → review+

Comment 3

4 years ago
Commit pushed to master at https://github.com/mozilla/popcorn.webmaker.org

https://github.com/mozilla/popcorn.webmaker.org/commit/22c86cf95fc07a22e44314f9a700e0d7ed2f7c54
Fix Bug 876909 - Pasting trackevents should attempt to maintain the same ordering and not add new layers

Updated

4 years ago
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Attachment mime type: text/plain → text/x-github-pull-request
You need to log in before you can comment on or make changes to this bug.