There is a bug in webkit (or at least Chrome) with a combination of border-radius , overflow: hidden and position other than static . Your twitter link uses a static position. Therefore, I would say that your only option is to use position: static . I modified your code to do this:
<div id="SuggestComplete"> <div id="SuggestProgressContainer"> <div id="SuggestProgressBar"> <div id="SuggestProgress"></div> </div> <span id="ProgressText">Follow 5 collections</span> </div> </div> <div id="button">test</div>
CSS
#SuggestProgressContainer { height: 27px; float: left; margin: 4px 20px 0 0; position: relative; top: 0; left: 0; width: 247px; } #SuggestProgressBar { width: 247px; height: 27px; background: #c6c6c6; border: 1px solid #bfbfbf; position: absolute; top: 0; left: 0; overflow: hidden; border-radius: 5px; -moz-border-radius: 5px; -webkit-border-radius: 5px; } #SuggestProgress { height: 100%; width: 50px; border: 1px solid #068CE1; background: #0F93E7; background: -webkit-gradient(linear, 0% 0%, 0% 100%, from(#1c9dee), to(#068ce1)); background: -webkit-linear-gradient(top, #1c9dee, #068ce1); background: -moz-linear-gradient(top, #1c9dee, #068ce1); background: -ms-linear-gradient(top, #1c9dee, #068ce1); background: -o-linear-gradient(top, #1c9dee, #068ce1); -webkit-transition: width 230ms ease-out; -moz-transition: width 230ms ease-out; -ms-transition: width 230ms ease-out; -o-transition: width 230ms ease-out; transition: width 230ms ease-out; }
This seems to work. Here is a demo .
The funny thing is that the problem described in the error report seems to be fixed, because then the problem occurred even without programmatically changing the width . But it seems that they too forgot to solve the problem on the events of the repander.
source share