Ticket #9783 (closed bug: invalid)
Getting dimensions of a cached picture
| Reported by: | anonymous | Owned by: | anonymous |
|---|---|---|---|
| Priority: | low | Milestone: | 1.next |
| Component: | css | Version: | 1.6.2 |
| Keywords: | Cc: | ||
| Blocking: | Blocked by: |
Description
When you load a cached picture (let says 50x50px) by: j('<img/>').load(function(){ alert(j(this).width()+' px : '+j(this).css('width')+' px'); }).attr({src:pathToPicture});
It returns: jquery1.5.2 -> 50 px : 50 px jquery1.6.2 -> 0 px : undefined px
Change History
comment:1 Changed 2 years ago by timmywil
- Owner set to anonymous
- Priority changed from undecided to low
- Status changed from new to pending
- Component changed from unfiled to css
comment:2 Changed 2 years ago by anonymous
- Status changed from pending to new
I suggest to change the priority to high. All my image loadings does not work for example.
About a test case with jsfiddle.net, jquery 1.6.2 is not provided (on July the 8th, 2011).
comment:3 Changed 2 years ago by timmywil
- Status changed from new to pending
Click the fork button. jQuery(edge) is the version that should be used for test cases.
comment:4 Changed 2 years ago by trac-o-bot
- Status changed from pending to closed
- Resolution set to invalid
Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.

Thanks for taking the time to contribute to the jQuery project! Please provide a reduced test case on http://jsfiddle.net that reproduces the issue experienced to help us assess your ticket.
Additionally, test against the jQuery (edge) version to ensure the issue still exists.