Ticket #7860 (closed bug: wontfix)
selector.css(name) returns inconsistently across browsers
| Reported by: | jason.lyle88@… | Owned by: | |
|---|---|---|---|
| Priority: | high | Milestone: | 1.5 |
| Component: | css | Version: | 1.4.4 |
| Keywords: | Cc: | ||
| Blocking: | Blocked by: |
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.
Change History
comment:1 Changed 2 years ago by rwaldron
- Priority changed from undecided to high
- Status changed from new to open
- Component changed from unfiled to css
- Milestone changed from 1.6 to 1.5
comment:2 Changed 2 years ago by rwaldron
- Status changed from open to closed
- Resolution set to wontfix
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
comment:3 Changed 2 years ago by rwaldron
http://www.w3.org/TR/css3-box/#the-lsquo0 thanks Dave Methvin for providing this
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.
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