You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IE requires two changes to fix this problem. First, the resize event needs to be attached to window instead of document. And the second fix is more for performance versus a requirement - but IE will call the resize event repeatedly for virtually every pixel change in the window dimension while the user resizes the browser. Here's the code to avoid that problem:
Not sure if fontresize can be attached to window so you'll want to test that, but the common timerid shouldn't conflict between the two events. You can also get away with adjusting the timeout duration to 250ms if you prefer a faster adjustment after the last pixel adjustment but I think on older systems with higher than normal cpu usage anything below 200 risks running the positionPlaceholder repeatedly.
The text was updated successfully, but these errors were encountered:
I tried to reproduce the issue you mentioned about IE not triggering the resize on the document. I can't reproduce that though. Don you have a testcase for that? Also: Which Version of jQuery are you using and which IE Version did you have this issue with?
I like your idea of throttling the window resize. I'll look into that.
IE requires two changes to fix this problem. First, the resize event needs to be attached to window instead of document. And the second fix is more for performance versus a requirement - but IE will call the resize event repeatedly for virtually every pixel change in the window dimension while the user resizes the browser. Here's the code to avoid that problem:
Not sure if fontresize can be attached to window so you'll want to test that, but the common timerid shouldn't conflict between the two events. You can also get away with adjusting the timeout duration to 250ms if you prefer a faster adjustment after the last pixel adjustment but I think on older systems with higher than normal cpu usage anything below 200 risks running the positionPlaceholder repeatedly.
The text was updated successfully, but these errors were encountered: