Opened 8 years ago

Closed 5 years ago

#8157 closed feature (wontfix)

Animation: Prevent numeric values from becoming negative

Reported by: SineSwiper1 Owned by:
Priority: minor Milestone: none
Component: ui.effects.core Version: 1.8.18
Keywords: Cc:
Blocked by: Blocking:

Description (last modified by Scott González)

IE8 appears to be fairly strict about erroring out on invalid negative values being put into CSS properties that don't allow negative values. Animation easing methods such as 'easeInOutElastic' will dip into the negative in certain animation frames, and if that CSS property is one of the non-negative values, IE8 will immediately error.

The following CSS properties cannot contain negative values, according to the W3C CSS2.1 standard (and certain CSS3 modules):

  • border-spacing
  • padding-top, padding-right, padding-bottom, padding-left, and padding
  • border-top-width, border-right-width, border-bottom-width, border-left-width, and border-width
  • border-top, border-right, border-bottom, border-left, and border (if specifying a width)
  • font-size and font (if specifying a size)
  • width and height
  • min-width, max-width, min-height, and max-height
  • line-height
  • outline-width and outline (if specifying a width)
  • widows

CSS3:

  • column-gap and column-rule-width
  • device-width, device-height, color, color-index, monochrome
  • marquee-play-count
  • background-size, border-image-slice, border-image-width, border-image-outset, box-shadow (only the blur radius)

Change History (6)

comment:1 Changed 8 years ago by Scott González

Description: modified (diff)
Reporter: changed from scott.gonzalez to SineSwiper1

comment:2 Changed 8 years ago by Scott González

As on jQuery 1.8, core will handle width, height, padding*, border*Width. We should add support for the other sane values (that means excluding things like widows and marquee-play-count).

comment:3 Changed 7 years ago by Scott González

Milestone: 1.9.01.10.0

comment:4 Changed 7 years ago by mikesherov

Status: newopen

comment:5 Changed 7 years ago by tj.vantoll

Milestone: 1.10.0none

comment:6 Changed 5 years ago by mikesherov

Resolution: wontfix
Status: openclosed

I'm going to close this as WONTFIX for now. IE9 is the last browser that complains. If anything, we should reopen this against jQuery Compat should users be having actual issues with the remaining uncovered properties in IE8 and IE9.

Note: See TracTickets for help on using tickets.