Skip to content
This repository has been archived by the owner on Apr 20, 2023. It is now read-only.
This repository has been archived by the owner on Apr 20, 2023. It is now read-only.

Box-sizing #216

Closed
yukulele opened this issue May 16, 2012 · 6 comments
Closed

Box-sizing #216

yukulele opened this issue May 16, 2012 · 6 comments

Comments

@yukulele
Copy link

My suggest : Add box-sizing support to PIE (for IE 6-7)

their is a .htc polyfill (https://github.com/Schepp/box-sizing-polyfill) and you can use it with PIE :

behavior: url('boxsizing.htc'), url('PIE.htc'); /*seam to works*/

but in some case they are conflictual (element is always resized on windows resize)
i think it was better to have this feature included in PIE.

@ttfkam
Copy link

ttfkam commented Aug 2, 2012

Along these lines, something I've run into is that PIE always assumes that box-sizing is never set. Therefore, if you do set "box-sizing: border-box;" to your document so that widths are consistent among all browsers, elements end up larger in IE than in newer browsers.

@kristianmandrup
Copy link

Perhaps you could integrate the HTC code found here ;)

https://github.com/Schepp/box-sizing-polyfill

@ttfkam
Copy link

ttfkam commented Aug 28, 2012

I should have commented earlier. I tried implementing this, but ran into a major stumbling block. If you change the width/height, you trigger a new PIE reflow. But you have to change it — clear element.runtimeStyle.width — in order to see what the dimensions actually are since JavaScript or some other style sheet rule may have overridden it in the meantime. Which triggers a PIE reflow. And so goes the merry-go-round of 100% CPU core utilization.

@kristianmandrup
Copy link

Couldn't you somehow set a special global state PIE.performReflow: false before you clear element.runtimeStyle.width, and then set it back to true when you are done?

@Soviut
Copy link

Soviut commented Dec 4, 2012

+1 for this.

@vtsaplin
Copy link

+1

@yukulele yukulele closed this as completed Sep 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants