css selectors - IE10 ignoring first-child in css and applying to all? -

What I'm trying to do is drop this down arrow with a select with this CSS Removes:

. Gender: First-child :: - MS-extension {display: none; }

The selected element has been disabled and its contents are programmatically set. It is still a selection due to our "unique" roll-own-binding approach which will be a huge overhaul to replace / update.

Actually I have basic information for a dynamic number of people. The first example is always the primary example, and its data comes from another section of the page, so it has been disabled and bound to values ​​in that other form. After this, every other entry is editable, it was thought to remove the drop down arrow from the first selection because they are only for reading. I know that the drop down arrow is missing that the selection is continuing but I still want to be there for every second selection which is not in vain.

I know that it works in a simplified way, but in my site everyone is selected, in the sections where their drop down arrow is hidden, what can I see in my site which is : First-child will circumvent the pseudo class? Why could this possibly work in Bella but not in the real place?

Anything I am reading asks you to examine your theory. My & lt ;! DOCTYPE html is public "- // W3C / / DTD HTML 4.0 Transitional // N" & gt; . Anyone who calls me the right method to use clearly, so it can not be 100% correct.

In addition, it only needs to work in IE10, it is an internal web app that will never run :

The single most common reason for each instance of a particular element is matching : first-escape , when only the first of them should match, then this That if each element is actually present in its container element, then here is an example:

Here, every . Gender is the first and only child of its original element, . Parent . On the other hand, . Parent Elements are the brothers and sisters of each other, not sharing the same basic element (not shown). Depending on the appearance of your source, it may be difficult to pinpoint the location of these basic elements within the source, but as long as your markup is not valid, they should be somewhere.

If this is triggered for the problem, fixing it is trivial - simply : first-child move the pseudo-class to the appropriate element:

 . Parent: first-child :: - MS-Extension {Display: None; }