Testing Backward Compatibility issues while Upgrading from Jquery 1.11.0 and Jquery UI 1.10.4 to Jquery 3.x and Jquery UI 1.12.xjQuery: IE 7 Compatibility Issue- $(window).resize firing event and locking upWebKit issues with event.layerX and event.layerYHow to work with jQuery and remain agnostic to its version?jQuery UI 1.8.22 with jQuery 1.8 doesn't have text in dialog buttonsUpdating JQuery to a newer version, but which one?What is the latest jQuery version to work with IE8?Upgrading to jQuery UI 1.12 broke slide() and drop() effectsHow can I add JAWS-compatible HTML form labels to month and day dropdowns in jQuery UI 1.10.4 datepickerTabs have full widthjQuery migration from 1.4.2 to latest
Is there a RAID 0 Equivalent for RAM?
Can I cause damage to electrical appliances by unplugging them when they are turned on?
Mimic lecturing on blackboard, facing audience
What is the difference between lands and mana?
Is this part of the description of the Archfey warlock's Misty Escape feature redundant?
Why does AES have exactly 10 rounds for a 128-bit key, 12 for 192 bits and 14 for a 256-bit key size?
Why Shazam when there is already Superman?
How to draw a matrix with arrows in limited space
Permission on Database
C++ check if statement can be evaluated constexpr
Has the laser at Magurele, Romania reached a tenth of the Sun's power?
How to get directions in deep space?
How do I fix the group tension caused by my character stealing and possibly killing without provocation?
Change the color of a single dot in `ddot` symbol
Multiplicative persistence
Are cause and effect the same as in our Universe in a non-relativistic, Newtonian Universe in which the speed of light is infinite?
"It doesn't matter" or "it won't matter"?
Do we have to expect a queue for the shuttle from Watford Junction to Harry Potter Studio?
What (the heck) is a Super Worm Equinox Moon?
What is the highest possible scrabble score for placing a single tile
awk assign to multiple variables at once
What fields between the rationals and the reals allow a good notion of 2D distance?
The IT department bottlenecks progress, how should I handle this?
Which was the first story featuring espers?
Testing Backward Compatibility issues while Upgrading from Jquery 1.11.0 and Jquery UI 1.10.4 to Jquery 3.x and Jquery UI 1.12.x
jQuery: IE 7 Compatibility Issue- $(window).resize firing event and locking upWebKit issues with event.layerX and event.layerYHow to work with jQuery and remain agnostic to its version?jQuery UI 1.8.22 with jQuery 1.8 doesn't have text in dialog buttonsUpdating JQuery to a newer version, but which one?What is the latest jQuery version to work with IE8?Upgrading to jQuery UI 1.12 broke slide() and drop() effectsHow can I add JAWS-compatible HTML form labels to month and day dropdowns in jQuery UI 1.10.4 datepickerTabs have full widthjQuery migration from 1.4.2 to latest
We have multiple sites running on Jquery 1.11.0 and Jquery UI 1.10.4. To fix the vulnerability issues reported by Chrome Developer Audit report, we want to upgrade to the latest stable versions. As suggested by Audit report these are Jquery 3.x and Jquery UI 1.12.x.
Is there any safe way we can upgrade Jquery and Jquery UI also check for back compatibility, so that it will not break any existing UI.
javascript jquery jquery-ui
add a comment |
We have multiple sites running on Jquery 1.11.0 and Jquery UI 1.10.4. To fix the vulnerability issues reported by Chrome Developer Audit report, we want to upgrade to the latest stable versions. As suggested by Audit report these are Jquery 3.x and Jquery UI 1.12.x.
Is there any safe way we can upgrade Jquery and Jquery UI also check for back compatibility, so that it will not break any existing UI.
javascript jquery jquery-ui
add a comment |
We have multiple sites running on Jquery 1.11.0 and Jquery UI 1.10.4. To fix the vulnerability issues reported by Chrome Developer Audit report, we want to upgrade to the latest stable versions. As suggested by Audit report these are Jquery 3.x and Jquery UI 1.12.x.
Is there any safe way we can upgrade Jquery and Jquery UI also check for back compatibility, so that it will not break any existing UI.
javascript jquery jquery-ui
We have multiple sites running on Jquery 1.11.0 and Jquery UI 1.10.4. To fix the vulnerability issues reported by Chrome Developer Audit report, we want to upgrade to the latest stable versions. As suggested by Audit report these are Jquery 3.x and Jquery UI 1.12.x.
Is there any safe way we can upgrade Jquery and Jquery UI also check for back compatibility, so that it will not break any existing UI.
javascript jquery jquery-ui
javascript jquery jquery-ui
edited Mar 7 at 6:30
Magnus Melwin
66411021
66411021
asked Mar 7 at 4:49
user1621791user1621791
3952921
3952921
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The simplest answer is no, you would need to test it out on a test server to detect and eliminate any side effects/bugs.
However that said, jQuery has had good backward compatibility. I have been using it for more than a few years now through its many releases of the core and have not had any breaking issues.
jQuery has been proactive with backward compatibility that they actually produce a backward compatibility plugin for each release.
Here's a reference for an upgrade guide to Jquery 3.x. Ref Upgrade Guide to Jquery 3.x
"Breaking changes" are always a problem.
– Salman A
Mar 7 at 5:24
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55036293%2ftesting-backward-compatibility-issues-while-upgrading-from-jquery-1-11-0-and-jqu%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The simplest answer is no, you would need to test it out on a test server to detect and eliminate any side effects/bugs.
However that said, jQuery has had good backward compatibility. I have been using it for more than a few years now through its many releases of the core and have not had any breaking issues.
jQuery has been proactive with backward compatibility that they actually produce a backward compatibility plugin for each release.
Here's a reference for an upgrade guide to Jquery 3.x. Ref Upgrade Guide to Jquery 3.x
"Breaking changes" are always a problem.
– Salman A
Mar 7 at 5:24
add a comment |
The simplest answer is no, you would need to test it out on a test server to detect and eliminate any side effects/bugs.
However that said, jQuery has had good backward compatibility. I have been using it for more than a few years now through its many releases of the core and have not had any breaking issues.
jQuery has been proactive with backward compatibility that they actually produce a backward compatibility plugin for each release.
Here's a reference for an upgrade guide to Jquery 3.x. Ref Upgrade Guide to Jquery 3.x
"Breaking changes" are always a problem.
– Salman A
Mar 7 at 5:24
add a comment |
The simplest answer is no, you would need to test it out on a test server to detect and eliminate any side effects/bugs.
However that said, jQuery has had good backward compatibility. I have been using it for more than a few years now through its many releases of the core and have not had any breaking issues.
jQuery has been proactive with backward compatibility that they actually produce a backward compatibility plugin for each release.
Here's a reference for an upgrade guide to Jquery 3.x. Ref Upgrade Guide to Jquery 3.x
The simplest answer is no, you would need to test it out on a test server to detect and eliminate any side effects/bugs.
However that said, jQuery has had good backward compatibility. I have been using it for more than a few years now through its many releases of the core and have not had any breaking issues.
jQuery has been proactive with backward compatibility that they actually produce a backward compatibility plugin for each release.
Here's a reference for an upgrade guide to Jquery 3.x. Ref Upgrade Guide to Jquery 3.x
edited Mar 7 at 5:18
answered Mar 7 at 5:11
Magnus MelwinMagnus Melwin
66411021
66411021
"Breaking changes" are always a problem.
– Salman A
Mar 7 at 5:24
add a comment |
"Breaking changes" are always a problem.
– Salman A
Mar 7 at 5:24
"Breaking changes" are always a problem.
– Salman A
Mar 7 at 5:24
"Breaking changes" are always a problem.
– Salman A
Mar 7 at 5:24
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55036293%2ftesting-backward-compatibility-issues-while-upgrading-from-jquery-1-11-0-and-jqu%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown