Apart from that, easing demos were fixed (PR #2320) and the test infrastructure has been migrated to jquery-test-runner (PR #2325).
If you're still on jQuery UI 1.13.x, see the jQuery UI 1.14.0 release blog post to learn about the changes in the 1.14.x line.
This release has been tested against jQuery 1.12.4, 2.2.4, 3.6.4, 3.7.1 & 4.0.0. Since jQuery follows semver, newer jQuery <5 versions within each major version line should generally work as well.
jQuery UI 1.14.2 triggers no jQuery Migrate messages except for its initialization one when running its test suite against jQuery 4.0.0 with jQuery Migrate 4.0.2 or jQuery 3.7.1 with jQuery Migrate 3.6.0, i.e. the latest versions at the time of this release.
Please remember jQuery UI is in a maintenance state: we’ll make sure the library is compatible with new jQuery releases and that security issues are fixed but no new significant feature work is planned. We’ll also try to fix important regressions from jQuery UI 1.12.1 or newer; older long-standing bugs may not get fixed. Note that this does not affect jQuery Core which is still actively maintained.
See the 1.14 Upgrade Guide for a list of changes that may affect you when upgrading from 1.13.x. For full details on what’s included in this release see the 1.14.2 Changelog.
Thanks to all who helped with this release, specifically: Michał Gołębiowski-Owczarek, Timmy Willison & Felix Nagel.
Note: please report bugs to the jQuery UI Bug Tracker; support questions should be posted on Stack Overflow with the jquery-ui tag.
]]>On January 14, 2006, John Resig introduced a JavaScript library called jQuery at BarCamp in New York City. Now, 20 years later, the jQuery team is happy to announce the final release of jQuery 4.0.0. After a long development cycle and several pre-releases, jQuery 4.0.0 brings many improvements and modernizations. It is the first major version release in almost 10 years and includes some breaking changes, so be sure to read through the details below before upgrading. Still, we expect that most users will be able to upgrade with minimal changes to their code.
Many of the breaking changes are ones the team has wanted to make for years, but couldn’t in a patch or minor release. We’ve trimmed legacy code, removed some previously-deprecated APIs, removed some internal-only parameters to public functions that were never documented, and dropped support for some “magic” behaviors that were overly complicated.
We have an upgrade guide and jQuery Migrate plugin release ready to assist with the transition. Please upgrade and let us know if you encounter any issues.
As usual, the release is available on our CDN and the npm package manager. Other third party CDNs will probably have it available soon as well, but remember that we don’t control their release schedules and they will need some time. Here are the highlights for jQuery 4.0.0.
jQuery 4.0 drops support for IE 10 and older. Some may be asking why we didn’t remove support for IE 11. We plan to remove support in stages, and the next step will be released in jQuery 5.0. For now, we’ll start by removing code specifically supporting IE versions older than 11.
We also dropped support for other very old browsers, including Edge Legacy, iOS versions earlier than the last 3, Firefox versions earlier than the last 2 (aside from Firefox ESR), and Android Browser. No changes should be required on your end. If you need to support any of these browsers, stick with jQuery 3.x.
jQuery 4.0 adds support for Trusted Types, ensuring that HTML wrapped in TrustedHTML can be used as input to jQuery manipulation methods in a way that doesn’t violate the require-trusted-types-for Content Security Policy directive.
Along with this, while some AJAX requests were already using <script> tags to maintain attributes such as crossdomain, we have since switched most asynchronous script requests to use <script> tags to avoid any CSP errors caused by using inline scripts. There are still a few cases where XHR is used for asynchronous script requests, such as when the"headers" option is passed (use scriptAttrs instead!), but we now use a <script> tag whenever possible.
It was a special day when the jQuery source on the main branch was migrated from AMD to ES modules. The jQuery source has always been published with jQuery releases on npm and GitHub, but could not be imported directly as modules without RequireJS, which was jQuery’s build tool of choice. We have since switched to Rollup for packaging jQuery and we do run all tests on the ES modules separately. This makes jQuery compatible with modern build tools, development workflows, and browsers through the use of <script type=module>.
These functions have been deprecated for several versions. It’s time to remove them now that we’ve reached a major release. These functions were either always meant to be internal or ones that now have native equivalents in all supported browsers. The removed functions include:
jQuery.isArray, jQuery.parseJSON, jQuery.trim, jQuery.type, jQuery.now, jQuery.isNumeric, jQuery.isFunction, jQuery.isWindow, jQuery.camelCase, jQuery.nodeName, jQuery.cssNumber, jQuery.cssProps, and jQuery.fx.interval.
Use native equivalents like Array.isArray(), JSON.parse(), String.prototype.trim(), and Date.now() instead.
The removal of deprecated APIs combined with the removal of code supporting old IE resulted in a size reduction of over 3k bytes gzipped.
The jQuery prototype has long had Array methods that did not behave like any other jQuery methods and were always meant for internal-use only. These methods are push, sort, and splice. They have now been removed from the jQuery prototype. If you were using these methods, $elems.push( elem ) can be replaced with [].push.call( $elems, elem ).
For a long time, browsers did not agree on the order of focus and blur events, which includes focusin, focusout, focus, and blur. Finally, the latest versions of all browsers that jQuery 4.0 supports have converged on a common event order. Unfortunately, it differs from the consistent order that jQuery had chosen years ago, which makes this a breaking change. At least everyone is on the same page now!
Starting with jQuery 4.0, we no longer override native behavior. This means that all browsers except IE will follow the current W3C specification, which is:
jQuery’s order in previous versions was: focusout, blur, focusin, focus. Ironically, the only browser to ever follow the old W3C spec (before it was updated in 2023) was Internet Explorer.
The slim build has gotten even smaller in jQuery 4.0.0 with the removal of Deferreds and Callbacks (now around 19.5k bytes gzipped!). Deferreds have long-supported the Promises A+ standard, so native Promises can be used instead in most cases and they are available in all of jQuery’s supported browsers except IE11. Deferreds do have some extra features that native Promises do not support, but most usage can be migrated to Promise methods. If you need to support IE11, it’s best to use the main build or add a polyfill for native Promises.
You can get the files from the jQuery CDN, or link to them directly:
https://code.jquery.com/jquery-4.0.0.js
https://code.jquery.com/jquery-4.0.0.min.js
You can also get this release from npm:
npm install jquery@4.0.0
Sometimes you don’t need ajax, or you prefer to use one of the many standalone libraries that focus on ajax requests. And often it is simpler to use a combination of CSS and class manipulation for web animations. Finally, all of jQuery’s supported browsers (except for IE11) now have support for native Promises across the board, so Deferreds and Callbacks are no longer needed in most cases. Along with the regular version of jQuery that includes everything, we’ve released a “slim” version that excludes these modules. The size of jQuery is very rarely a load performance concern these days, but the slim build is about 8k gzipped bytes smaller than the regular version. These files are also available in the npm package and on the CDN:
https://code.jquery.com/jquery-4.0.0.slim.js
https://code.jquery.com/jquery-4.0.0.slim.min.js
These updates are already available as the current versions on npm and Bower. Information on all the ways to get jQuery is available at https://jquery.com/download/. Public CDNs receive their copies today, please give them a few days to post the files. If you’re anxious to get a quick start, use the files on our CDN until they have a chance to update.
Lots of wonderful people have contributed to jQuery and its associated projects in the past 20 years and many of us met up for a reunion in Dallas. John Resig even joined over Zoom. This release was posted while we were all together.

Full changelog: 4.0.0
processData: true even for binary data (ce264e07)headers for script transport even when cross-domain (#5142, 6d136443)null as success functions in jQuery.get (#4989, 74978b7e).attr( name, false ) remove for all non-ARIA attrs (#5388, 063831b6)toggleClass(boolean|undefined) signature (#3388, a4421101)$.parseHTML from document.implementation to DOMParser (0e123509)src/ (#5262, f75daab0)
(d0ce00cd)<col> elements (#5628, eca2a564)selector.js wrapper (53cf7244)offsetHeight( true ), etc. include negative margins (#3982, bce13b72)undefined for whitespace-only CSS variable values (#5120) (7eb00196)addClass( array ), compress code (#4998, a338b407)show, hide & toggle methods in the jQuery slim build (297d18dd)getStackHook to getErrorHook (#5201, 258ca1ec).hover() using non-deprecated methods (fd6ffc5e)3.x-stable (d9281061)trac-NUMBER references (eb9ceb2f)#NUMBER Trac issue references with trac-NUMBER (5d5ea015).preventDefault() in beforeunload (7c123dec).on(focus).off(focus) (#4867, e539bac7):has; test both on iPhone & iPad (65e35450)jQuery.expr[ ":" ]/jQuery.expr.filters (329661fd)selector.js module depend on attributes/attr.js (#5379, e06ff088)selector.js depenencies from various modules (e8b7db4b)qSA again (#5177, 09d988b7)uniqueSort chainable method (#5166, 5266f23c):has if CSS.supports(selector(...)) non-compliant (#5098, d153c375)jQuery.get( String, null-ish, null-ish, String ) (05325801)jQuery.get( String, null-ish, null-ish, String ) (76687566)hidden="until-found" attr tests from 3.x-stable (3a31866b):has selector tests with 3.x-stable (f2d9fde5)cssSupportsSelector test (716130e0)It’s here! Almost. jQuery 4.0.0-rc.1 is now available. It’s our way of saying, “we think this is ready; now poke it with many sticks”. If nothing is found that requires a second release candidate, jQuery 4.0.0 final will follow. Please try out this release and let us know if you encounter any issues.
A 4.0 upgrade guide and jQuery Migrate release are also now available, but both are subject to changes before the final jQuery Core release.
Many of the breaking changes in jQuery 4.0.0 are ones the team has wanted to make for years, but couldn’t in a patch or minor release. We’ve trimmed legacy code (including removing support for IE before version 11), removed some previously-deprecated APIs, removed some internal-only parameters to public functions that were never documented, and dropped support for some “magic” behaviors that were overly complicated.
As usual, the release is available on our CDN and the npm package manager. Third party CDNs will not be hosting this rc release, but will host the 4.0.0 final release later. Here are some highlights for jQuery 4.0.0 rc.1.
You can get the files from the jQuery CDN, or link to them directly:
https://code.jquery.com/jquery-4.0.0-rc.1.js
https://code.jquery.com/jquery-4.0.0-rc.1.min.js
You can also get this release from npm:
npm install jquery@4.0.0-rc.1
Sometimes you don’t need ajax, or you prefer to use one of the many standalone libraries that focus on ajax requests. And often it is simpler to use a combination of CSS and class manipulation for web animations. Finally, all of jQuery’s supported browsers (except for IE11) now have support for native Promises across the board, so Deferreds and Callbacks are no longer needed in most cases. Along with the regular version of jQuery that includes everything, we’ve released a “slim” version that excludes these modules. The size of jQuery is very rarely a load performance concern these days, but the slim build is about 8k gzipped bytes smaller than the regular version. These files are also available in the npm package and on the CDN:
https://code.jquery.com/jquery-4.0.0-rc.1.slim.js
https://code.jquery.com/jquery-4.0.0-rc.1.slim.min.js
These updates are already available as the current versions on npm. Information on all the ways to get jQuery is available at https://jquery.com/download/. Public CDNs receive their copies today, please give them a few days to post the files. If you’re anxious to get a quick start, use the files on our CDN until they have a chance to update.
Thank you to all of you who participated in this release by submitting patches, reporting bugs, or testing, including ac-mmi, Michał Gołębiowski-Owczarek, neogy-akash, and the whole jQuery team.
Full changelog: 4.0.0-rc.1
$.parseHTML from document.implementation to DOMParser (0e123509)3.x-stable (d9281061).preventDefault() in beforeunload (7c123dec)jQuery.expr[ ":" ]/jQuery.expr.filters (329661fd)box-sizing set to content-box (issue #2277, PR #2281) and makes the tabs widget work correctly with IDs with backslashes (PR #2307). Dialog supports a new option: uiDialogTitleHeadingLevel. When set to a number between 1 & 6, it changes the current <span> wrapper of the dialog title into a heading element of a specified level (issue #2271, PR #2275). We've also enabled GitHub CodeQL checks and fixed a few reported issues.
Apart from that, there have been a number of fixes to demos available on jqueryui.com, mostly accounting for the back compat flag being off by default.
If you're still on jQuery UI 1.13.x, see the jQuery UI 1.14.0 release blog post to learn about the changes in the 1.14.x line.
This release has been tested against jQuery 1.12.4, 2.2.4, 3.6.4 & 3.7.1. Since jQuery follows semver, newer jQuery <4 versions within each major version line should generally work as well.
jQuery UI 1.14.1 triggers no jQuery Migrate warnings when running its test suite against jQuery 3.7.1 with jQuery Migrate 3.5.2, i.e. the latest versions at the time of this release.
Please remember jQuery UI is in a maintenance state: we’ll make sure the library is compatible with new jQuery releases and that security issues are fixed but no new significant feature work is planned. We’ll also try to fix important regressions from jQuery UI 1.12.1; older long-standing bugs may not get fixed. Note that this does not affect jQuery Core which is still actively maintained.
See the 1.14 Upgrade Guide for a list of changes that may affect you when upgrading from 1.13.x. For full details on what’s included in this release see the 1.14.1 Changelog.
Thanks to all who helped with this release, specifically: Daniel García, Michał Gołębiowski-Owczarek, Ralf Koller, Timmy Willison & Felix Nagel.
Note: please report bugs to the jQuery UI Bug Tracker; support questions should be posted on Stack Overflow with the jquery-ui tag.
]]>jQuery UI 1.14 finally drops support for all versions of Internet Explorer & Edge Legacy. Only the latest version of Chrome, Firefox, Safari & Edge are officially supported. Contrary to what we did in past releases, code supporting unsupported browsers has been deleted.
Support for jQuery 1.7-1.11, 2.0-2.1 & 3.0-3.5 has been dropped.
This release has been tested against jQuery 1.12.4, 2.2.4, 3.6.4 & 3.7.1. Since jQuery follows semver, newer jQuery <4 versions within each major version line should generally work as well.
jQuery UI 1.14 triggers no jQuery Migrate warnings when running its test suite against jQuery 3.7.1 with jQuery Migrate 3.5.2, i.e. the latest versions at the time of this release.
Backward compatibility with the 1.11 API is disabled by default. To enable it (restoring the default 1.13 behavior), set the jQuery.uiBackCompat flag to true. We encourage trying without the compatibility layer, though - maybe your app is already using new APIs exclusively? If there are any feature gaps from the old APIs, please submit issues.
A few APIs have been removed as they were no longer needed after dropping IE support: $.fn._form, $.ui.ie, $.ui.safeActiveElement & $.ui.safeBlur. See the 1.14 Upgrade Guide for information about replacements.
The Download Builder now only supports jQuery UI 1.12 & newer. This change happened independently from the jQuery UI 1.14 release, but it's worth reminding.
Modal dialogs now get the aria-modal="true" attribute added. Thanks to that, modal dialogs cause the elements outside of the dialog to be excluded from the accessibility tree, making some accessibility tools more useful. See issue #2246 for more information.
jQuery UI 1.14 is tested in all supported browsers & jQuery Core versions not only post-merge as was done in the past, but also on every pull request via GitHub Actions. That should make contributing to jQuery UI easier.
This improvement was made possible by a major rewrite of jQuery UI test infrastructure, which removed all deprecated or under-supported dependencies.
Please remember jQuery UI is in a maintenance state: we’ll make sure the library is compatible with new jQuery releases and that security issues are fixed but no new significant feature work is planned. We’ll also try to fix important regressions from jQuery UI 1.12.1; older long-standing bugs may not get fixed. Note that this does not affect jQuery Core which is in active development.
See the 1.14 Upgrade Guide for a list of changes that may affect you when upgrading from 1.13.x. For full details on what’s included in this release see the 1.14.0 Changelog.
Thanks to all who helped with this release, specifically: Michał Gołębiowski-Owczarek, Porter Clevidence, Ralf Koller, Timmy Willison, and Felix Nagel.
Note: please report bugs to the jQuery UI Bug Tracker; support questions should be posted on Stack Overflow with the jquery-ui tag. Please don’t use comments to report bugs.
If you have feedback on us doing our release for jQuery UI 1.14.0, feel free to leave a comment below. Thank you.
]]>Last February, we released the first beta of jQuery 4.0.0. We’re now ready to release a second, and we expect a release candidate to come soon
. This release comes with a major rewrite to jQuery’s testing infrastructure, which removed all deprecated or under-supported dependencies. But the main change that warranted a second beta was a fix to the exports field for bundlers. More on that and other changes below.
Many of the breaking changes in jQuery 4.0.0 are ones the team has wanted to make for years, but couldn’t in a patch or minor release. We’ve trimmed legacy code (including removing support for IE before version 11), removed some previously-deprecated APIs, removed some internal-only parameters to public functions that were never documented, and dropped support for some “magic” behaviors that were overly complicated.
We will publish a comprehensive upgrade guide before final release, to outline the removed code and how to migrate. The jQuery Migrate plugin will also be ready to assist. For now, please try out this release and let us know if you encounter any issues.
As usual, the release is available on our CDN and the npm package manager. Third party CDNs will not be hosting this beta release, but will host the 4.0.0 final release later. Here are some highlights for jQuery 4.0.0 beta.2.
There are many different ways to include jQuery in a project. Supporting all of them can be difficult, especially when the environment supports both CommonJS and ESM modules. We wanted to support all of the ways jQuery might be included, whether using a named export or the default export. Also, we wanted to ensure jQuery was only ever included once, even when jQuery was both imported using ESM and required using CommonJS in the same environment or bundle. We think we’ve worked out a solution that supports Node.js and bundlers like rollup, webpack, and parcel. More details can be found in the PR. Also, we created a wiki page to explain how the exports property in jQuery’s package.json will work in 4.0.
The HTML spec defines boolean attributes that often correlate with boolean properties. If the attribute is missing, it correlates with the false property value, if it’s present – the true property value. The only valid values for boolean content attributes are empty string or the full attribute name (e.g. checked="checked").
jQuery has historically tried to be helpful here and treated boolean attributes in a special way in the .attr() API:
false was passed;The problem is the spec occasionally converts boolean attributes into ones with additional attribute values with special behavior – one such example is the new "until-found" value for the hidden attribute. Our setter normalization meant passing those values was impossible with .attr() (.prop() was unaffected). Also, new boolean attributes were introduced occasionally and jQuery could not easily add them to the list without incurring breaking changes.
This patch removes any special handling of boolean attributes – the getter returns the value as-is and the setter sets the provided value, with one exception. To maintain backwards compatibility, this patch makes the false boolean value trigger attribute removal for ALL non-ARIA attributes. For example, .attr( "checked", false ) will continue to remove the checked attribute, which is the only way the corresponding property will be set to false. ARIA attributes are exempt from the rule since many of them recognize the string "false" as a valid value with semantics different than the attribute missing. To remove an ARIA attribute, use .removeAttr() or pass null as the value to .attr().
jQuery 4.0.0-beta.2 also fixes some inconsistent behavior when finding the position of elements within tables. The offset parent on which the position was based could change depending on whether the element’s position style was static or relative.
<div id="container" style="position: relative;">
<table>
<tr>
<td>
<span id="static"></span>
<span id="relative" style="position: relative;"></span>
</td>
</tr>
</table>
</div>
Previously, $('#static').position() was returning the position relative to the containing <td> element, while $('#relative').position() was returning the position relative to #container.
Now, both elements return their position relative to #container.
You can get the files from the jQuery CDN, or link to them directly:
https://code.jquery.com/jquery-4.0.0-beta.2.js
https://code.jquery.com/jquery-4.0.0-beta.2.min.js
You can also get this release from npm:
npm install jquery@4.0.0-beta.2
Sometimes you don’t need ajax, or you prefer to use one of the many standalone libraries that focus on ajax requests. And often it is simpler to use a combination of CSS and class manipulation for web animations. Finally, all of jQuery’s supported browsers (except for IE11) now have support for native Promises across the board, so Deferreds and Callbacks are no longer needed in most cases. Along with the regular version of jQuery that includes everything, we’ve released a “slim” version that excludes these modules. The size of jQuery is very rarely a load performance concern these days, but the slim build is about 8k gzipped bytes smaller than the regular version. These files are also available in the npm package and on the CDN:
https://code.jquery.com/jquery-4.0.0-beta.2.slim.js
https://code.jquery.com/jquery-4.0.0-beta.2.slim.min.js
These updates are already available as the current versions on npm. Information on all the ways to get jQuery is available at https://jquery.com/download/. Public CDNs receive their copies today, please give them a few days to post the files. If you’re anxious to get a quick start, use the files on our CDN until they have a chance to update.
Thank you to all of you who participated in this release by submitting patches, reporting bugs, or testing, including Michał Gołębiowski-Owczarek, J.Son, Liam James and the whole jQuery team.
jQuery has a Mastodon account! We now post releases and other updates to both X and Mastodon. Also, you may be interested in following some of our team members that have Mastodon accounts.
jQuery: https://social.lfx.dev/@jquery
mgol: https://hachyderm.io/@mgol
timmywil: https://hachyderm.io/@timmywil
Full changelog: 4.0.0-beta.2
:has selector tests with 3.x-stable (f2d9fde5)Compared to the first beta, there are two main changes:
aria-modal attribute in dialogs have been added (PR #2257).We’ve also finalized the migration from the TestSwarm test runner to our custom one integrated into GitHub Actions.
See the jQuery UI 1.14.0-beta.1 blog post for information about changes already available in the first beta.
Please remember jQuery UI is in a maintenance state. We’ll make sure the library is compatible with new jQuery releases and that security issues are fixed but no new significant feature work is planned. We’ll also try to fix important regressions from jQuery UI 1.12.1; older long-standing bugs may not get fixed. Note that this does not affect jQuery Core, which is still actively maintained.
For full details on what’s included in this release see the 1.14.0-beta.2 Changelog. The 1.14 Upgrade Guide will be available later.
Thanks to all who helped with this release, specifically: Ralf Koller, Michał Gołębiowski-Owczarek, Timmy Willison.
Note: Please report bugs to the jQuery UI Bug Tracker. Support questions should be posted on Stack Overflow with the jquery-ui tag.
]]>This release doesn't offer any new features, only the following breaking changes:
This beta is not integrated into the jQuery UI Download Builder; support for jQuery UI 1.14 will be added before the final release. Because of that, zip bundles are not available for this beta.
We'd also like to remind you that beginning in June 2024, the Download Builder will only support jQuery UI 1.12 or newer. For more information, please read the Plans for jQuery UI 1.14 blog post.
Please remember jQuery UI is in a maintenance state. We’ll make sure the library is compatible with new jQuery releases and that security issues are fixed but no new significant feature work is planned. We’ll also try to fix important regressions from jQuery UI 1.12.1; older long-standing bugs may not get fixed. Note that this does not affect jQuery Core, which is still actively maintained.
For full details on what’s included in this release see the 1.14.0-beta.1 Changelog. The 1.14 Upgrade Guide will be available later.
Thanks to all who helped with this release, specifically: Michał Gołębiowski-Owczarek, Timmy Willison, Felix Nagel.
Note: Please report bugs to the jQuery UI Bug Tracker. Support questions should be posted on Stack Overflow with the jquery-ui tag.
]]>The above issues, combined with the fact very few people work on jQuery UI in their limited time, result in delays—1 year and 9 months have passed between the 1.13.2 and 1.13.3 releases. If we want to continue supporting jQuery UI, we need to reduce some of this complexity.
We are planning the following changes to ease the maintenance effort:
We understand these changes may be disrupting for some teams. However, we need to balance limited resources with still being able to address more important issues. We think the above plan is the best way to achieve this goal.
]]>jQuery UI has a new test runner ported from jQuery that allows local & BrowserStack test runs without reliance on Karma. As an added bonus, we're now running tests against Chrome, Firefox, Safari & Edge against latest jQuery 1.x, 2.x, 3.x & the development version in GitHub CI, allowing to detect more issues at the pull request level. This will also be a basis for a future jQuery UI 1.14 - but that's a topic for a separate blog post.
Please remember jQuery UI is in a maintenance state: we’ll make sure the library is compatible with new jQuery releases and that security issues are fixed but no new significant feature work is planned. We’ll also try to fix important regressions from jQuery UI 1.12.1; older long-standing bugs may not get fixed. Note that this does not affect jQuery Core which is still actively maintained.
See the 1.13 Upgrade Guide for a list of changes that may affect you when upgrading from 1.12.x. For full details on what’s included in this release see the 1.13.3 Changelog.
Thanks to all who helped with this release, specifically: Ashish Kurmi, DeerBear, divdeploy, Kenneth DeBacker, mark van tilburg, Matías Cánepa, Michał Gołębiowski-Owczarek, Timmy Willison, Timo Tijhof, Дилян Палаузов, Felix Nagel.
Note: please report bugs to the jQuery UI Bug Tracker; support questions should be posted on Stack Overflow with the jquery-ui tag.
]]>