Bug Tracker

Custom Query (13852 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (34 - 36 of 13852)

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Ticket Resolution Summary Owner Reporter
#4700 worksforme Tests #25 and #26 fail in jQuery test suite, in Opera 9.64 (Mac) znerd
Description

Steps to reproduce:

Expected results:

  • All tests are run and succeed.

Actual results:

Results of test #25:

core module: width() (1, 8, 9) Test set to 30 correctly: 30 Test negative width ignored: 30 Test padding specified with pixels: 30 Test border specified with pixels: 30 Test padding specified with ems: 30 Test border specified with ems expected: 30 actual: 8 Test padding specified with percent: 30 Test hidden div: 30 Test child width with border and padding: 20

Results of test #26:

core module: height() (1, 7, 8) Test set to 30 correctly: 30 Test negative height ignored: 30 Test padding specified with pixels: 30 Test border specified with pixels: 30 Test padding specified with ems: 30 Test border specified with ems expected: 30 actual: 8 Test padding specified with percent: 30 Test hidden div: 30

#12202 duplicate jQuery 1.8rc1 is considered invalid znerd
Description

While validating the jQuery 1.8rc1 .js file, I got some errors:

  1. Parse error. invalid property id at input line 5795 : 15
  2. Parse error. syntax error at input line 5795 : 16
  3. Parse error. syntax error at input line 5796 : 9
  4. Parse error. missing name after . operator at input line 7917 : 27
  5. Parse error. syntax error at input line 7918 : 17
  6. Parse error. missing ) in parenthetical at input line 7936 : 4
  7. Parse error. syntax error at input line 9222 : 1

Looking at the source it's clear that line 5795 is indeed causing a problem: 'throws' is used as an identifier, while it is also a JavaScript keyword. Something similar applies to line 7917/7918, where 's.throws' is used as a condition.

Line 9222 is the last line of the file.

#8368 worksforme Regression: speed fix for $.trim results in incorrect behavior with non-breaking spaces IE [email protected]
Description

The fix for ticket 6868 (slow trim when trimming very large strings) looks like it undid the fix for ticket 4980, which solved the problem of IE not properly handling all whitespace characters correctly in its '\w' character class (namely anything that isn't a plain space, e.g. unicode or non-breaking spaces).

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