Skip to main content

Bug Tracker

Side navigation

#7093 closed bug ()

Opened September 28, 2010 11:01AM UTC

Closed November 11, 2010 11:09PM UTC

Last modified March 13, 2012 08:04PM UTC

Chrome and Opera outerWidth calculation problem on refresh

Reported by: muratcorlu Owned by:
Priority: low Milestone:
Component: dimensions Version: 1.4.2
Keywords: chrome, opera, outerWidth, refresh Cc:
Blocked by: Blocking:
Description

We set a div's width by a different element's width using jQuery's outerWidth function. But when we refresh page on Google Chrome(6.0) and Opera(10.62), outerWidth function gives wrong value. This problem only occurs on refreshing pages manually, not click links or directly openning page. Here is a live example page: http://www.sahibinden.com/secure-e-trade/

Attachments (0)
Change History (9)

Changed September 29, 2010 10:08PM UTC by snover comment:1

milestone: 1.4.3
need: ReviewTest Case
priority: undecidedlow

Please provide a reduced test case.

Changed October 14, 2010 03:13AM UTC by snover comment:2

status: newpending

This ticket has been marked as missing a test case. In an effort to reduce the number of outstanding tickets in the bug tracker, it will be closed automatically in 30 days. In order to prevent this from happening, please provide a working test case. If a test case has already been provided and our records are wrong, please respond to the ticket so that it can be fixed. Thank you!

Changed November 11, 2010 11:09PM UTC by trac-o-bot comment:3

status: pendingclosed

Automatically closed due to 14 days of inactivity.

Changed February 17, 2011 08:11PM UTC by misza comment:4

Hi,

I'm experiencing the same problem with the width not displayed correctly when manually refreshed the page.

Can anybody let me know how to add the testcase?:)

Cheers,

Michal

Changed February 17, 2011 08:17PM UTC by jitter comment:5

_comment0: Replying to [comment:4 misza]: \ > Can anybody let me know how to add the testcase?:) \ [http://docs.jquery.com/How_to_Report_Bugs How to report bugs]1297973923420719

Replying to [comment:4 misza]:

Can anybody let me know how to add the testcase?:)

How to report bugs. Test case ideally on http://jsfiddle.net

Changed February 17, 2011 08:26PM UTC by misza comment:6

Damn, I'm not sure how I missed the big red frame, answering my very question... :)

Thank you for your reply!

Changed February 17, 2011 09:52PM UTC by miszacus comment:7

I just managed to find a solution to the same problem as described in the description. The problem was related to the order of includes in the head section - first were the js files and then the css file. The solution is to simply put the css file before the js.

The problem occurred on Chrome 9.0, it was fine on Firefox 3.6 - both Ubuntu 10.10 (x64).

Changed March 09, 2011 10:38AM UTC by anonymous comment:8

Replying to [comment:7 miszacus]:

I just managed to find a solution to the same problem as described in the description. The problem was related to the order of includes in the head section - first were the js files and then the css file. The solution is to simply put the css file before the js. The problem occurred on Chrome 9.0, it was fine on Firefox 3.6 - both Ubuntu 10.10 (x64).

Legend! That's hours of hair pulling out the window until this is fixed 'properly'. Thanks!

Changed July 09, 2011 08:35PM UTC by Shelly Skeens comment:9

Replying to [comment:8 anonymous]:

Replying to [comment:7 miszacus]: > I just managed to find a solution to the same problem as described in the description. The problem was related to the order of includes in the head section - first were the js files and then the css file. The solution is to simply put the css file before the js. > > The problem occurred on Chrome 9.0, it was fine on Firefox 3.6 - both Ubuntu 10.10 (x64). Legend! That's hours of hair pulling out the window until this is fixed 'properly'. Thanks!

This fixed a similar issue I was having with border calculations in Chrome 12.0. Another thanks!