Do nothing, and let Microsoft and their customers sort it out.
When Microsoft makes a (potential) blunder so many Web developers seem feel it's their responsibility to work around it. It's not. Microsoft and the IE team try hard not to "break the Web". If they missed, chances are very good they'll fix it. If not, it's not your responsibility to work around the breakage.
Has this been a problem for you in practice? Have you had user complaints about it? If not, why are you worried about it? If so, tell your users to work it out with Microsoft or try another browser.
We're serving ads so working across as many browsers as possible is important to us. Also from a customer service perspective, telling a client that ads won't work on their site because of feature X in browser Y isn't always the best option.
IE8 isn't that wide spread yet so it hasn't been a problem in practice, but we are working on a solution to address this in case the inprivate blocking becomes very popular in the wild.
We are handling this problem in exactly the same way that we handle people running no-script and/or super high security settings - ignore them. It's such a minimal problem as to be worthless to resolve.
Comments
Do nothing, and let Microsoft and their customers sort it out.
When Microsoft makes a (potential) blunder so many Web developers seem feel it's their responsibility to work around it. It's not. Microsoft and the IE team try hard not to "break the Web". If they missed, chances are very good they'll fix it. If not, it's not your responsibility to work around the breakage.
Has this been a problem for you in practice? Have you had user complaints about it? If not, why are you worried about it? If so, tell your users to work it out with Microsoft or try another browser.
We're serving ads so working across as many browsers as possible is important to us. Also from a customer service perspective, telling a client that ads won't work on their site because of feature X in browser Y isn't always the best option.
IE8 isn't that wide spread yet so it hasn't been a problem in practice, but we are working on a solution to address this in case the inprivate blocking becomes very popular in the wild.
We are handling this problem in exactly the same way that we handle people running no-script and/or super high security settings - ignore them. It's such a minimal problem as to be worthless to resolve.