How can input clear button be hidden if IE10 is being run in IE7, IE8, or IE9 modes?


  • A customer has requested that the IE10's new clear button not appear on input boxes in our application. Microsoft and others indicate that a way to remove it is to use the ::-ms-clear pseudo-element, as shown below:



      width : 0;

      height: 0;


    However, this only works if the browser is running in IE10 mode.

    Our application has been in production for a number of years. It turns out that our application is incompatible with IE10 in various areas. Our simple fix was to run it in IE8 mode, i.e. add this line to the top of every page: 

         <meta http-equiv="X-UA-Compatible" content="IE-EmulateIE8"

    The result is that the input clear button is still there. 

    In IE10 mode, the button disappears - but our application won't work in this mode.

    The conceptual question is: if these other modes (like IE8) allows IE10 to operate like IE8 andthus not recognize pseudo-elements like "::-ms-clear", then why would it still display the clear button? 

    The practical questions are 1) Can Microsoft change its browser code so that the input clear button (and the other new buttons) don't appear if the browser is running in some "earlier" mode, and 2) Can Microsoft device a way to programatically eliminate the input clear button for browsers running in these earlier modes? 



    Thursday, June 06, 2013 12:16 PM


All replies

  • input::-ms-clear{display:none}

    add a valid document type to your pages and validate and correct the markup so they render in 'standards', not IE10 Quirks or IE5 Quirks.



    Thursday, June 06, 2013 10:11 PM
  • i had put HTML5 DTD (<!DOCTYPE html>).

    and my codes are correct and validated.

    But it doesn't work in IE7,8,9.

    how can i fix it? T. T

    Thursday, June 27, 2013 8:46 AM
  • Same thing is Happening To me as well

    as INPUT::-ms-clear

    is clearing it out just on IE10 but not on older versions, my HTML is Valid and its using <!DOCTYPE html>

    we need a fix here!

    Tuesday, November 19, 2013 10:46 AM