#15766 closed defect (bug) (fixed)
jQuery UI 1.8.7
Reported by: | demetris | Owned by: | |
---|---|---|---|
Milestone: | 3.1 | Priority: | normal |
Severity: | normal | Version: | 3.1 |
Component: | External Libraries | Keywords: | has-patch |
Focuses: | Cc: |
Description
jQuery UI 1.8.7 was released earlier today:
http://blog.jqueryui.com/2010/12/jquery-ui-1-8-7/
I cannot tell myself whether it would be a safe update so late in the 3.1 dev cycle. I am attaching a patch anyway.
I have applied the patch to two sites of mine, to see how things look.
PS. I cannot find the JavaScript component. What happened to it?
Attachments (1)
Change History (7)
#3
@
14 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
This change was deployed to WordPress.com today, and resulted in
"Uncaught jQuery UI Tabs: Mismatching fragment identifier."
on http://newyork.cbslocal.com/
#5
@
14 years ago
- Resolution set to fixed
- Status changed from reopened to closed
Closing as fixed.
Likely an issue with the existing JS that possibly affected UI versions < 1.8.7. The theme will need to be fixed. We can only address problems with core (wp-admin).
#6
@
14 years ago
Background on the fragment identifier problem: As a result of the fix for <a href="http://bugs.jqueryui.com/ticket/6710">this bug</a>, jQuery UI is more strict about parentage. The issue is that UI.tabs expects the links to the tabs and the containers of tab content to have the same parent element. Well, really it’s that the element on which the tabs instance is initialized must be an ancestor of both the links and the tab contents containers. If you see this error you need to fix your theme/plugin.
Updates jQuery UI from 1.8.6 to 1.8.7