Search and Top Navigation
#8157 closed feature (wontfix)
Opened March 02, 2012 10:39AM UTC
Closed November 18, 2014 05:14PM UTC
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
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)
Attachments (0)
Change History (6)
Changed March 02, 2012 10:40AM UTC by comment:1
description: | 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) → 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) \ |
---|---|
reporter: | scott.gonzalez → SineSwiper1 |
Changed May 25, 2012 02:33AM UTC by comment:2
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).
Changed October 11, 2012 02:42PM UTC by comment:3
milestone: | 1.9.0 → 1.10.0 |
---|
Changed October 19, 2012 09:11PM UTC by comment:4
status: | new → open |
---|
Changed January 25, 2013 09:23PM UTC by comment:5
milestone: | 1.10.0 → none |
---|
Changed November 18, 2014 05:14PM UTC by comment:6
resolution: | → wontfix |
---|---|
status: | open → closed |
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.