Rectangle 27 1

That's most likely the "best" way. But keep in mind that it's not just alpha-trans that IE6 doesn't implement properly when it comes to PNG files; the color space is corrupt due to IE not implementing the gamma properly, and thus PNG files often show "darker" than they should. One alternative "solution" that we implemented on a recent project was to mark every png image with a "toGif" class, in the CSS of which a custom behavior .htc is called which changes the .png extension to .gif if the browser is detected to be one we've marked as a problem. We just include a GIF version of every PNG alongside it in the same path, and if the browser is found to be one that doesn't handle PNGs properly, it swaps it out with a GIF version of the image. We therefore sacrifice the alpha blending in favor of guaranteed full-on transparency and color accuracy, and only do so when we know it's probably not going to look right as-is. It may not be an ideal solution, but it's the nature of cross-browser I suppose. Edit: Actually now that I look at the project in question, we used an .htc behavior for an img class called "alpha" as well which tosses the correct filter on the image automatically. So you're detecting the browser using javascript instead of an IE6-only pure CSS hack, so it might be a little bit more elegant... but it's basically the same thing. For an introduction to how to write DHTML behaviors, try this link.

html - IE6 issues with transparent PNGs - Stack Overflow

html css internet-explorer-6 png
Rectangle 27 1

To addition of htc solutions mention above, here're another solutions and examples to reach rounded corners in IE.

cross browser - Creating rounded corners using CSS - Stack Overflow

css cross-browser rounded-corners css3
Rectangle 27 1

To addition of htc solutions mention above, here're another solutions and examples to reach rounded corners in IE.

cross browser - Creating rounded corners using CSS - Stack Overflow

css cross-browser rounded-corners css3
Rectangle 27 1

If you have coded specifically against IE 6 (working around issues, using non-standard features), it may be a little rough, but IE 8 is infinitely better in terms of stability and standards support.

Along with moving to IE 8, consider supporting other reasonably compliant browsers such as Firefox, Opera, Safari, or Chrome. IE 8 isn't a bad product, but other browsers will "keep you honest" and help you avoid hacks and also expose you to features not supported by IE 8.

It's also worth noting that pretty much any framework you may already be using (if it's still being maintained) will have equal or better support for IE 8. Same goes for any third party components which render HTML/script.

Lastly, I would also spend some time with IE 9 to understand the direction that Microsoft is going with the product. Most IE 8 apps will work fine with IE 9, but there are some subtle differences (mostly fixing/reinterpreting style and layout implementations in IE 8).

Edit: Here's an excellent, free tool I use for running different versions of IE side by side:

Here are several things off the top of my head that are non-standard IE extensions. These will probably still work in IE 8, but keep in mind that Microsoft is making a big push towards standards compliance, and they aren't guaranteed to work in the future. Also, other browsers don't support them at all.

Again, to my knowledge none of these things have been removed from IE 8 but they are all red flags for future maintainability.

Tim, thank you for the link and the comments. Unfortunately, we aren't using any framework. That's why it hurts so much :). From the link, I understand that we won't have a problem in CSS, because there is not any feature that would broke backward compatibility. what about the JavaScript and HTML? Am I going to have any problem with that? Or should I just add IE8 to my "compatible browsers" list :).

@sahs - I would start with checking for the obvious things (if you haven't already) like invalid HTML and script errors. There's also a great free tool for running IE versions side-by-side that will let you test, fix, and compare results. I will update my post with the link.

internet explorer 8 - Differences Between IE6 and IE8 - Stack Overflow

internet-explorer-8 internet-explorer-6 cross-browser
Rectangle 27 2

The solution was so simple. Setting priority to largest integer number (2147483647) instead of largest value defined by Google (1000), in manifest file solves the problem, and phone doesn't dial last number by double clicking and broadcast receiver detects the headset button double click.

        android:enabled="true" >
        <intent-filter android:priority="2147483647">
            <action android:name="android.intent.action.MEDIA_BUTTON" />

android - How to detect headset button double click in HTC phones with...

android android-broadcast headset
Rectangle 27 1

As most Android devices are probably personal devices and Facebook considers itself a personal service, Facebook's Single-Sign-On is a nice way so the user does not have to log in for each Facebook-Connected App he uses (because usually he would use them with the same account anyway)

However, Facebook's API-SDK for Android does offer you a decent logout() method within the provided Facebook-Class which you can use, if you really want to force-sign-out the user. Due to the Single-Sign-On, the User should be logged out on all his SSO-Facebook-Applications, including FriendStream.

IMHO that might be a bit rude, though :)

HTC FriendStream Facebook app interferes with my Android App Facebook ...

android cookies login facebook facebook-graph-api
Rectangle 27 1

<IfModule mod_headers.c>
    Header set X-UA-Compatible "IE=edge"
    # `mod_headers` can't match based on the content-type, however, we only
    # want to send this header for HTML pages and not for the other resources
    <FilesMatch "\.(appcache|crx|css|eot|gif|htc|ico|jpe?g|js|m4a|m4v|manifest|mp4|oex|oga|ogg|ogv|otf|pdf|png|safariextz|svgz?|ttf|vcf|webapp|webm|webp|woff|xml|xpi)$">
        Header unset X-UA-Compatible

internet explorer - Misunderstand of internet-explorer browser meta-tags msdn

Rectangle 27 0

Despite your comments elsewhere on this question, this isn't actually a bug in IE; it's handling the relative path perfectly rationally.

The reason this issue happens is because the two URLs (ie with and without the slash) are actually in different directories as far as the URL path is concerned.

So as far as the browser is concerned, the two URLs are in different directory paths. And therefore, if you specify a relative path, it will be relative to different paths in each, and one of them will clearly not point to the right place. If you have other items with relative paths, such as images, they would also have the same issue, and it will be in all browsers, not just IE. (I assume, therefore, that you don't have many other relative paths on this page)

The quick solution, as you already worked out, is to turn it into an absolute path, starting with a slash. This will ensure it's loaded from the same location in the site regardless of what the URL is that you load it from.

However, the question hints at a bigger issue. A well-behaved site should not allow both of those URLs to be valid. The URL without a slash should redirect to the URL with a slash; it should not simply load the same content regardless of whether there's a slash or not.

Allowing both URLs to load the same content is explicitly bad for your site's SEO. It means that Google will see your site as having two pages with the same content, and this in turn is counted as a minus point for your google rankings.

The issue is easy to resolve using .htaccess/mod_rewrite, and ideally, you would resolve this issue with as much urgency as the original CSS3Pie loading issue.

Thanks Spudley, this was ultimately the issue. I tried adjusting the path to an image on the page, and I was able to verify what you've described.

@ima007 - no problem. glad I was of some help :)

internet explorer 8 - CSS3 PIE - behavior HTC file doesn't load when s...

css3 internet-explorer-8 internet-explorer-7 css3pie
Rectangle 27 0

Not really sure I understand what you're after but I use Curvy Corners to curve my corners in IE. It's relaly simple, it reads any of the -webkit- corner attributes in your CSS and applies it to IE.

At least they promise exactly what I'm looking for and examples are loading pretty swiftly on IE8. I'll try this mechanism and report back.

css - How to get only one rounded corner with border-radius htc hack a...

css internet-explorer
Rectangle 27 0

I'm not doing much HTML programming myself, but I googled a bit, and IE does not support hovering the way you're trying to go it. I found the following webpage: which appears to give a solution to it. You can google for "HTC file", and "HTC file example" and the first hit on each search seems to give you essentially what you wanted.

IE8 (at least, in normal mode) does support it just fine. (I don't have other versions to test, but you can try it yourself at:

cross browser - Css IE6IE7/IE8 hover problem - Stack Overflow

css cross-browser
Rectangle 27 0

Are you using any behaviors in your CSS? I've seen behaviors bring an app to its knees if too many are used and/or if they affect too many elements. Check for any .htc files lurking around.

Of course behaviors only pertain to IE and they use JavaScript, so I'm sure different IE versions handle them more competently than others.

html - How can I troubleshoot Rendering Performance issues in IE - Sta...

html windows performance internet-explorer rendering
Rectangle 27 0

HTC with IE

IE and Firefox both contain ways to execute JavaScript from CSS. As Paolo mentions, one way in IE is the expression technique, but there's also the more obscure HTC behavior, in which a seperate XML that contains your script is loaded via CSS. A similar technique for Firefox exists, using XBL. These techniques don't exectue JavaScript from CSS directly, but the effect is the same.

body {

and within that file have something like:

   <PUBLIC:ATTACH EVENT="ondocumentready" ONEVENT="main()" LITERALCONTENT="false"/>
   function main() 
     alert("HTC script executed.");

The HTC file executes the main() function on the event ondocumentready (referring to the HTC document's readiness.)

Firefox supports a similar XML-script-executing hack, using XBL.

Use a CSS rule like so:

body {
  -moz-binding: url(script.xml#mycode);

and within your script.xml:

<?xml version="1.0"?>
<bindings xmlns="" xmlns:html="">

<binding id="mycode">
      alert("XBL script executed.");


All of the code within the constructor tag will be executed (a good idea to wrap code in a CDATA section.)

the code doesn't execute unless the CSS selector matches an element within the document


(Not sure if asking on a old answer is helpful) I tried the XBL technique in Firefox 18, but it didn't work. Is it only accessible to Firefox extensions?

Using Javascript in CSS - Stack Overflow

javascript css
Rectangle 27 0

But it still requires a script loaded as an HTC behaviour.

Anyway, my best answer is just to leave the corners squared in IE (by the way, it seems IE9 will support border radius) applying the graceful degradation principle.

We used CSS3Pie and find it excellent (see my separate answer). I was originally all in favour of the graceful degradation option, but our designers were insistent that the site had to look identical in all supported browsers. They were quite stubbon about it. Fortunately CSS3Pie solved the problem.

css - Rounded Corners in IE 7+ with/without javascript? - Stack Overfl...

css design
Rectangle 27 0

.menu {
    border-color: #598FD1 #598FD1 #1A53A2;
    border-style: solid;
    border-width: 2px 1px 3px;
    height: 18px;
    margin-left: 318px;
    margin-top: 10px;
    padding: 14px;
    text-align: center;
    width: 914px;
    background-color: #2A72D8;
    background-image: -webkit-gradient(linear, left top, left bottom, from(#2A72D8), to(#1A53A2));
    background-image: -webkit-linear-gradient(top, #2A72D8, #1A53A2);
    background-image:    -moz-linear-gradient(top, #2A72D8, #1A53A2);
    background-image:     -ms-linear-gradient(top, #2A72D8, #1A53A2);
    background-image:      -o-linear-gradient(top, #2A72D8, #1A53A2);
    background-image:         linear-gradient(top, #2A72D8, #1A53A2);
    -webkit-box-shadow: inset 0px 0px 9px #2A72D8;
     -moz-box-shadow: inset 0px 0px 9px #2A72D8;
          box-shadow: inset 0px 0px 9px #2A72D8;
    -webkit-border-radius: 4px;
     -moz-border-radius: 4px;
          border-radius: 4px;
    -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;
    behavior: url(css/;

llich-Thanks for your suggestions.It worked well and one problem is in IE it looks somethink like blurred.So any thing need to change in IE.

@Kiran IE does not support CSS3, you can polyfill your way through a bit like you did with the .htc polyfill in your CSS but it will never look as in the other browsers. You can give CSS3 Pie a chance, it is one of the most complete polyfills i've seen around.

html - Working with CSS3 Menu - Stack Overflow

html css css3 menu
Rectangle 27 0 file is not compressed, if you do it the file size will decrease to 4-5kb

css - Is there any other better way than this (modernizr 7 KB javascri...

javascript css xhtml
Rectangle 27 0

If you are going to add CSS3 behaviors to older IE browsers, you really do not have any choice but to use shims like PIE. Whether it is good practice or not really doesn't apply. The question really is, "can I do it?"

I'm currently using PIE for the same reasons you are. It works very well for features that it supports. There is one thing to watch out for. On my site I'm primarily using PIE for rounded corners and gradient backgrounds. Probably 60% of content is generated via templates. So containers holding the generated html can vary greatly in size as dynamic content is being created. PIE doesn't seem to render this situation reliably on IE8 (haven't tested with IE6/7). It works correctly 50 to 90% of time, but I cannot get to 100%. For the pages with static html content, PIE works excellently.

So for a "normal" web page, I'd go with PIE.

The PIE's generated corners look really great. Exactly same as in FF/Chrome/IE9

I just took a look at modernizr. Their list of "shims" is awesome!

internet explorer - Are Microsoft .htc files a good idea? - Stack Over...

internet-explorer css3pie
Rectangle 27 0

Try this polyfill from Louis Remi which affords IE versions background-size abilities. It works wonders for me on my projects. It's a simple .htc file (and maybe an .htaccess file, depending on your server configuration).

javascript - Internet Explorer background size issue - Stack Overflow

javascript html css internet-explorer
Rectangle 27 0

You know you can use a htc hack to get border-radius support in IE

I haven't used it myself yet but it's supposedly supported in IE6, 7, and 8. So the following should cover everything.

.rounded {
-webkit-border-radius: 9px;  /* safari-chrome */ 
 -moz-border-radius: 9px;   /* firefox */ 
 border-radius: 9px;  /* opera */ 
 behaviour:url(; /* IE hack */ 

I read your question correctly the first time. You didn't state the reasons why you were against js, and while htc files contain js, in practice they are not used the same. Since this was tagged semantic-markup I thought it deserved a mention.

HTC and javascript both need javascript enabled. Why i need without JS because client need this

Just in case anyone else reads this, I have since tried on a couple of different sites. Be warned that it is very fickle, I didn't have much luck with it.

css - What is the second best possible way to make this Content Box's ...

css xhtml semantic-markup