Bug Tracker

Custom Query (13852 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (37 - 39 of 13852)

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Ticket Resolution Summary Owner Reporter
#15208 duplicate jQuery.extend Michael
Description

File: index.hmtl

<!DOCTYPE html>
<html>
  <head>
    <meta charset="utf-8">
    <title>Test for jQuery.extend</title>
  </head>
  <body>
    <script src="MyLibrary.js" type="text/javascript"></script>
    <script src="//cdn.jsdelivr.net/jquery/1.11.1/jquery.min.js" type="text/javascript"></script>
  </body>
</html>

File: MyLibrary.js

(function (document) {

  // region To Debug

  function debug(text, args) {
    for (var buffer = [], count = args.length, index = 0; index < count; )
      buffer.push(args[index++]);
    if (count)
      text += '\n' + buffer.join('\n');
    document.body.appendChild(document.createElement('pre')).innerHTML = text
  }

  // endregion

  // region MyLibrary extensions

  // Static extension: Object.extend(target: Object, source: Object, ...): Object
  Object.extend = function () {
    debug('Object.extend is called', arguments)
  };

  // Instance extension: ({ ... }).extend(source: Object, ...): Object
  Object.prototype.extend = function () {
    debug('Object.prototype.extend is called', arguments)
  };

  // endregion

})(document);
#15205 migrated No way to globally clean up data m_gol
Description

When an element data is leaked (for example because it was detached/off-DOM and we lost reference to it) there is no way to get rid of its data. This matters in tests run in watch mode as leaks can accumulate & crash the browser.

The only alternative now seems to be initializing jQuery from scratch when we desire a clean environment. This is a little difficult now due to the fact that jQuery doesn't expose any initializing function so the lib would have be loaded once again (which, again, is not so easy/natural in many test frameworks).

Angular 1.3 betas were recently switched to use jQuery 2.1 instead of 1.x and this problem has arisen; see: https://github.com/angular/angular.js/issues/8532

#15204 cantfix Binding an event from an iframe content to its parent.window not working properly cm0s
Description

If we bind an event from an iframe content to its parent window and use a property set on the iframe content window in order to update a counter (eg. window.counter), whenever we refresh the iframe page the counter property doesn't seem to be correctly reinitialized. The iframe page should set the window.counter to 0 each time the page is reloaded, but the counter property seems to keep previous value.

I've been able to reproduce this issue on Chrome and Opera. On IE and Firefox there is no issue.

To better expose this issue I created a fiddle snippet: http://jsfiddle.net/cm0s/WYy6U/3/

To reproduce the issue, first try to click outside the iframe: the counter will increment by 1 each time a click event is triggered. Then, click multiple times on the "Reload this page" link and then click outside the iframe. You will see the counter is now incremented by the number of times you clicked on the link not by 1 as it should.

The same snippet with the use of standard javascript onclick event instead of the $.on() function perfectly works on Chrome, Opera, IE, Firefox : http://jsfiddle.net/cm0s/D6j5G/1/

Tested browser :

  • Opera 23.0.1522.60 (doesn't work)
  • Chrome 36.0.1985.125 (doesn't work)
  • IE 11.0.9600.17207 (work correctly)
  • Firefox 31 (work correctly)

All jQuery versions seem to be impacted (branches 2.x and 1.x)

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Note: See TracQuery for help on using queries.