Turkiyenin en sevilen filmlerinin yer aldigi porno internet sitemiz olan ve sex tarzi bir site olan sitemiz gercekten dillere destan bir durumda herkesin sevdigi bir site olarak tarihe gececege benziyor. Sitenin en belirgin ozelliklerinden birisi de Turkiyede gercekten kaliteli ve muntazam, duzenli siteleri olmamasidir. Bu yuzden iste. Ayrica en net goruntu kalitesine sahip adresinde yayinlanmaktadir.
Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.
In RC1 & 2 the form field upper/lower borders are missing (sometimes just the top one depending) in IE8 in compat mode. I can change the mode to 8 and the borders are fine as expected. I have a neighbor pull up the same in IE7 and it's fine so just seems to be compat mode IE8. Sadly, most of our company is on IE8 and IT enforces compatibility mode on all intranet sites via Group Policy.
Happens in form panels, toolbars, etc.
Is there any way you can look at the form field styling in IE8 strict during this last run towards GA? I'll be your best friend...
Here is what I'm seeing when I pull up the Dynamic Forms example from the SDK. Also here is a screenshot of IE's developer tools panel to show how it's loading up by default.
*BTW, I just posted asking how Ext JS renders up within IE using Chromeframe. Today chromeframe is blocked on our corp machines. But, if Ext JS renders up in IE using Chromeframe as if it were native Chrome then I might lobby for IT to open it as a permitted add-on. http://www.sencha.com/forum/showthre...C2-Chromeframe
Thx. Looks like doing some custom CSS for when our tools are opened in IE8 (some folks are permitted to use FF) might be the way I'll have to go.
For reference below is what the form looks like when I load up 4.1 Beta 3. The field styling was ok in 4.1 Beta 1, 2, and 3 and I think the Preview release prior to that. It was also ok in 4.0.7, 4.0.6, 4.0.2, 3.4, and 2.2.
Any chance you guys can take one more look at it before GA? 4.1 RC1 is the first place I started having the field styling require unique CSS solutions for IE. I've got a handful of projects I did in 4.0.x and am hoping for as smooth as possible a migration over to 4.1.
Ok. Was thinking it fell into the unsupported realm. Guess I lucked out over the past few releases with the field styling.
I did discover a way to opt a page out of IE8's "compat mode on intranet sites" option in case anyone else comes across this post.
You can add the following tag to your page:
<meta http-equiv="X-UA-Compatible" content="IE=8" />
or from what I've read the following header response:
I know this fixes the field styling for our users on IE8. Don't know what it does to users who are still on IE7. Will have to test once back in the office next week. Though I think we still have about 30k users on IE7 so hopefully this works for them, too.