Side navigation
#7860 closed bug (wontfix)
Opened December 29, 2010 02:12PM UTC
Closed January 07, 2011 06:09PM UTC
Last modified January 07, 2011 06:13PM UTC
selector.css(name) returns inconsistently across browsers
| Reported by: | jason.lyle88@gmail.com | Owned by: | |
|---|---|---|---|
| Priority: | high | Milestone: | 1.5 |
| Component: | css | Version: | 1.4.4 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
When a percentage value is used in CSS, the value returned depends on the browser. With webkit browsers, the percentage value is returned. With other browsers, the pixel value is returned. To see this in action, you can run the following in any webkit based browser, and then any other browser.
I am unsure of what the correct behavior should be, but my best guess would be consistently returning a pixel value. Usually computations depend on a value, not a percentage.
Attachments (0)
Change History (3)
Changed January 07, 2011 04:38PM UTC by comment:1
| component: | unfiled → css |
|---|---|
| milestone: | 1.6 → 1.5 |
| priority: | undecided → high |
| status: | new → open |
Changed January 07, 2011 06:09PM UTC by comment:2
| resolution: | → wontfix |
|---|---|
| status: | open → closed |
I think the best resolution is to create a cssHook if you need to access min-/max- property values. These css properties won't change unless you change them within your logic. Additionally, they are not available in IE6
Changed January 07, 2011 06:13PM UTC by comment:3
http://www.w3.org/TR/css3-box/#the-lsquo0 thanks Dave Methvin for providing this
Confirmed. http://jsfiddle.net/rwaldron/c6RQT/
jQuery 0 GIT, 1.4.4, 1.4.3, 1.4.2, 1.3.2, 1.2.6
WebKit: 50%
FireFox: 288.5px