#23830 closed enhancement (fixed)
Update to Backbone 1.0.0
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 3.6 | Priority: | normal |
Severity: | normal | Version: | 3.6 |
Component: | External Libraries | Keywords: | |
Focuses: | Cc: |
Description
Backbone 1.0.0 was released today.
I've done a cursory test of the media modal and the current state of revisions and everything appears to be working fine.
Attachments (2)
Change History (13)
#4
@
12 years ago
- Keywords has-patch needs-testing added; needs-patch removed
This should get us most of the way there. I think there still may be a rough edge or two; please test and record what you find.
#5
@
12 years ago
- Owner set to nacin
- Resolution set to fixed
- Status changed from new to closed
In 23893:
#6
follow-up:
↓ 10
@
12 years ago
I tried to debug this, but seems like it's beyond my backbone skills. After the 1.0.0 update in [23893], the Attachments
collection has always got one more element than it should, resulting in an weird empty element on all media screens: http://cl.ly/image/3x033D2i0H3t
#10
in reply to:
↑ 6
@
12 years ago
- Keywords needs-patch removed
- Resolution set to fixed
- Status changed from reopened to closed
Replying to kovshenin:
After the 1.0.0 update in [23893], the
Attachments
collection has always got one more element than it should, resulting in an weird empty element on all media screens: http://cl.ly/image/3x033D2i0H3t
Let's handle this in #24094.
That's not the case — Collections were changed to fire "set" instead of "reset", which is causing a bunch of breakage. The patch doesn't bust the cache, so you were likely still seeing 0.9.10.