Side navigation
#13126 closed bug (wontfix)
Opened December 28, 2012 04:27AM UTC
Closed January 28, 2013 08:26PM UTC
css('float') is different when element is static,absolute,fixed in different browsers
Reported by: | vince.t.malone@gmail.com | Owned by: | mikesherov |
---|---|---|---|
Priority: | low | Milestone: | None |
Component: | css | Version: | 1.8.2 |
Keywords: | Cc: | mikesherov | |
Blocked by: | Blocking: |
Description
$(el).css('float') is different in different browsers when element is absolute or fixed. If element is floated left and an absolute position, $(el).css('float') returns "left" in Chrome but "none" in all other major (up-to-date) browsers.
example: http://jsfiddle.net/ChPCD/7/
Attachments (0)
Change History (6)
Changed December 28, 2012 01:45PM UTC by comment:1
cc: | → mikesherov |
---|
Changed December 28, 2012 06:46PM UTC by comment:2
component: | unfiled → css |
---|---|
owner: | → mikesherov |
priority: | undecided → low |
status: | new → assigned |
Definitely a WEBKIT bug, as it's in Safari too. Good catch. Float's resolved value is it's computed value, so this should return none. It would be pretty easy for us to pave over this with a cssHook if you guys think it's worth it. I'm guessing 20 bytes or so. @dmethvin, thoughts?
I'll check webkit for a bug report and submit if not.
Changed December 28, 2012 07:10PM UTC by comment:3
Changed January 06, 2013 11:54PM UTC by comment:4
@mikesherov, do you want to try a patch for this? I'm okay with a wontfix as well, it's a pretty rare case.
Changed January 07, 2013 12:11AM UTC by comment:5
Ill patch it. We need SOME patches now that oldIE is gone :P
Changed January 28, 2013 08:26PM UTC by comment:6
resolution: | → wontfix |
---|---|
status: | assigned → closed |
Actually, I'm not going to patch this considering the webkit bug is almost fixed at this point: https://bugs.webkit.org/show_bug.cgi?id=105836
THE SYSTEM WORKS.
Looks like a Chrome bug to me. Have you reported it in their bug tracker? I didn't see it or anything like it in a search. http://code.google.com/p/chromium/issues/list
http://www.w3.org/TR/css3-positioning/ Section 8:
In any case there's a simple workaround, not sure it's worth a special case inside jQuery for this but looping in mikesherov for his opinion.