Width is inconsistant with node isn't in the document

Reported by:	dsmlover@gmail.com	Owned by:
Priority:	low	Milestone:	None
Component:	css	Version:	1.7
Keywords:		Cc:
Blocked by:		Blocking:

Description

If I do .width() on an element that is not attached to the document where the width is set by a css class chrome returns 0 and firefox returns the correct width.

http://jsfiddle.net/X8hqd/4/

I don't know if jQuery should be responsible but it should be known.

Attachments (0)

Change History (4)

Changed November 14, 2011 04:30PM UTC by rwaldron comment:1

I'm certain this is a duplicate, but I can't find the original ticket.

Changed November 14, 2011 04:30PM UTC by rwaldron comment:2

component:	unfiled → css

Changed November 14, 2011 07:19PM UTC by timmywil comment:3

_comment0:	It must be kept in mind that .css is for retrieving _computed_ values. Both webkit and firefox (and every browser) return 0 for the computed width of disconnected, as they should. An element that is not connected cannot have width. We provide fallbacks to uncomputed styles where they are available, but on a disconnected node with no inline styles, there are no uncomputed styles to fall back to, at least in webkit. → 1321298358619308
priority:	undecided → low
resolution:	→ cantfix
status:	new → closed

It must be kept in mind that .css is for retrieving _computed_ values. Both webkit and firefox (and every browser) return 0 for the computed width of disconnected elements, as they should. An element that is not connected cannot have width. We provide fallbacks to uncomputed styles where they are available, but on a disconnected node with no inline styles, there are no uncomputed styles to fall back to, at least in webkit.

Changed November 14, 2011 07:29PM UTC by anonymous comment:4

If that is the case I believe we should not provide those fallbacks then. Just like we are removing layerX and layerY because it doesn't work across browsers I think this should be removed too.

Thanks for your time.

Side navigation