Ask Learn
Preview
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign inThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The information published in this post is now out-of-date and one or more links are invalid.
—IEBlog Editor, 21 August 2012
Hello, I am Kun, the first developer of IE Beijing team in Microsoft. Our team has been working on the Intrinsic Controls of IE in the past year. Among these controls, the SELECT element has been greatly improved. IE6’s SELECT element didn’t support certain properties, like z-index, title, and zoom. In IE7, we have re-worked the SELECT element. This new version has features and fixes that will make IE7 a better user experience. This is work that has long been requested by web developers and it is certainly something that should have been addressed in past releases. In IE7 the work on the SELECT element along with our work on CSS is part of our focus to supply web developers with a consistent platform for great web solutions.
We are continuing to refine the Windowless SELECT elements and we are very proud of it. This should make web and application developers happier since this will allow them to have the Select control perform Z-order and Zoom the way it was intended to without elaborate workarounds and hacks. If you were one of those people relying on the Windowed Select element in your code, you should be aware of this change so as to make sure your sites and applications continue to work with IE7.
In IE7, we have taken a feature (SELECT element) that every internet user has run into in some form or another and made it work better for everyone. We did this without introducing new user behaviors or specific programmatic alterations that would force thousands of web developers to have to change their sites. Essentially, if it worked in IE6, it should work the same or even better in IE7.
SELECT element in IE7 - An Overview
In IE6, the HTML <SELECT> element was implemented through the Windows Shell ListBox and Combobox controls. Some key features were missing in the old version of the SELECT element, such as proper support for z-index, TITLE support, and zoom. Web developers had to write complex CSS and scripts to workaround these issues.
In IE7 however, we re-implemented the <SELECT> element to make IE7 more standards-compliant. This new version does not use any Shell controls any more. In fact, it is implemented totally through the MSHTML framework, including styling, UI interaction, and rendering. Thus the SELECT element in IE7 is more of an HTML element than the former legacy control.
SELECT element in IE7 - Windowless and Z-order
A big problem of IE6’s SELECT element was that it could not perform z-index.
Here is an illustration.
When a user moved the mouse over to the “Mouse Over Here” in figure 1, this triggered the select element. Z-Index=1 should be behind and hidden by the select element (which appears as a yellow box) while Z-index = 3 should appear visible above the select element.
Instead with the legacy Windowed element you will find these two SELECT elements always placed on top of the floating DIV, even though the DIV has a higher z-index value.
Figure 1 IE6 Select Behavior (you can still see Z-Index=1 even though it should be behind Z-Index=2 layer)
Floating DIV tags (or other block elements) are a common technique used to write DHTML menus. But with this issue, web developers had to be careful not to put any SELECT element below these menus or else they would get obstructed. Although a work around with complex scripts was possible, it was inconvenient and kludgy.
This issue comes from the fact that the SELECT element in IE6 is a window based control, which always stays above the content of its parent IE window.
The Windowless Select Element
In IE7, the SELECT element has been changed into a windowless element. This means that Listbox and the inline part of Combobox are laid out and rendered directly by MSHTML. In other words, they are drawn directly within content flow. This new windowless SELECT element will follow the z-index priority in the markup. The following screen shot shows how the sample markup above will look in IE7.
Fig 2 IE7 Select Behavior (Z=Index = 1 is now hidden beneath Z-Index=2 the way it is supposed to be)
The main thing that you should take away from this posting is that the Windowless SELECT element is coming to replace the Windowed SELECT element in IE7. If your web or application developers adhered to normal HTML procedures in calling the SELECT element, then it should be fine. What worked in IE6 should work better in IE7. If you were using workarounds calling on the Windowed SELECT API, you may need to re-inspect your code to make sure that it doesn’t break on IE7.
We’d love to hear any comments, feedback or experiences that you’ve had with the SELECT Element or even Z-Order so that we can continue to improve this great feature.
- Kun Cong
Anonymous
January 01, 2003
I'm waiting to test the version 7 of IE, hope good
Anonymous
January 01, 2003
Nothing wrong with that. Too bad it'll be used most for overlay ads.
On a side note, does IE7 still have a problem where if a page uses Unicode characters (e.g. math symbols, etc.), the characters will be shown as boxes unless another font is specified? (Example: [http://us.metamath.org/mpeuni/clim4a.html]. Other Browsers smartly switch to fonts with those characters, but IE forces them to make separate, server-taxing pages with GIFs, e.g. [http://us.metamath.org/mpegif/clim4a.html] so viewers can see the glyphs in their glory.)
Anonymous
January 01, 2003
Game Kid, when I go to the link above in a current IE7 build, I don't see any boxes around the math symbols.
- Al Billings [MSFT]
Anonymous
January 01, 2003
Do <option> elements now feature the ability to change styles as well? IE6, of course, supports some styling of <option> elements, but is quite limited, and no where near where other, more recent browsers are.
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
How about nested <optgroup>? Are you going to add support for that, too?
Keep the good work, guys! The whole IE Team is doing something I couldn't believe would happen anytime soon - I'm eager to use IE again, years after dropping it in favor of Mozilla (Seamonkey) and Firefox.
Best regards
Anonymous
January 01, 2003
Opt-groups seem to work with IE6 on XPSP2. http://cita.rehab.uiuc.edu/software/mozilla/test/ts-test-page-input.php
Type-ahead item selection would be a nice improvement.
Anonymous
January 01, 2003
can you say animated gif??? pictures are good, video is better.
Anonymous
January 01, 2003
This will be a welcome improvement.
One other (positive) consequence of this change should be reduced resource consumption. Of course on XP it's not as big a deal compared to 9x, but every little bit helps.
Anonymous
January 01, 2003
Woohoo! Wow, this makes me very happy. Talk about a bug that is basically impossible to work around... this one has driven me up the wall for some time.
Thanks, and keep the good news coming!
~ Tim
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
I wanted to point out that the screenshots above have a visual flaw that might be misleading. The IE6 example is shown with Windows Themes enabled (hence the "shiny" look on the dropdown button) and the IE7 example is shown with Windows Theming disabled (hence the flat gray look).
IE7's select control ~does~ support Windows Themes but Themes just happened to be turned off on the test machine used to generate the IE7 screenshot.
Max: I believe there are ways to simulate a combobox using script, but this is not something we're going to be able to make native for IE7. There's always IE8. :-)
Grady: Disabled OPTION elements do not appear to be available in IE7.
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
I'm agreed with Clayton here - the ability to properly style optgroup elements (including padding) would be really nice.
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
re Igor Abade's request for nested optgroups. The w3c specs specifically disallow nested optgroups. from the specs, "groups may not be nested".
http://www.w3.org/TR/html4/interact/forms.html#edef-OPTGROUP
hey, MS - how about rejigging those multi-selects, while you're at it? see here: http://verens.com/archives/2005/04/27/son-of-multiselect/
Anonymous
January 01, 2003
When the SELECT element becomes windowless, what happens when it needs to drop down over the borders of it's hosting window?
Background is a security concern: If you can hide it (partly) behind another div with higher z-index, are able apply more styles to it and could drop it down with a script you could use it for instance to drop over the status bar and spoof/hide something.
Anonymous
January 01, 2003
Wow! I am very excited!
Finally :-)
All the people that paste negative stuff about the fixing of the z-index bug, make your site compliant with all browsers! Do not make sites for just 1 browser (that really dumb ;) )!
IE team, Good job! I'd like to see more coming :-)
Anonymous
January 01, 2003
Good job in making the <select> windowless as other visual elements.
Pitty that combobox is not available in IE7 (Or should I say, HTML spec.?). In many case it'll be handy to have just that.
Yes it can be scripted, but it'll be neater to have the elements within the element, not in a place outside the DOM(the client side script).
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
Great! (although that was rather lenghty explanation for just one bug removed...)
How about fixing <button> now? Default type submit, support for value, sending value only when clicked...?
<button> is horribly buggy, even worse buggy than MSDN documents it's buggyness :)
Anonymous
January 01, 2003
@EricLaw,
> To make a page render correctly internationall, it helps to make sure that you choose a font that contains the character you want to display
That means font fallback doesn't work properly. The web developer can't know what fonts are installed on the user's machine, so the whole idea is that if the proper glyphs aren't found in the current font, then a suitable font's glyphs are substituted instead.
Does Internet Explorer 7 do the right thing regarding the issues noted on the following page?
http://girtby.net/archives/2005/10/07/internet-explorer-makes-me/
> (Arial is often a good bet)
I believe you mean Arial Unicode MS, yes?
Anonymous
January 01, 2003
@Jim-- To be honest, I'm a networking guy and I know very little about font fallback; what little I've learned comes from dealing with IDN display issues.
I can say that the page you've referenced renders correctly ("not-implies" character and all) in current builds of IE7.
I'm afraid I can't speak to the exact font-fallback algorithm in IE7, but I know that there was a team working on that for IE7 and it appears that their efforts resolved many of these issues.
Anonymous
January 01, 2003
> Pitty that combobox is not available in IE7
> (Or should I say, HTML spec.?). In many case
> it'll be handy to have just that.
Now that this control is done through MSHTML, it seems like the IE7 team should take some initiative and add an editable attribute to allow editing the text in the textbox.
Anonymous
January 01, 2003
The width of the SELECT element often needs to be set because of screen design concerns. Just as often, the width of the text in the OPTION tags is greater than this width.
In IE, this means that the text of each option is cut off. With other browsers, as the dropdown options display when you activate the control, the width increases so that option text is completely visible.
Consider this usability concern in balancing other requests for this control.
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
Thanks for another great post!
How about styling on the arrow of the select menu? That has always been annoying (in all browsers).
Perhaps the BG color for the main color and the color attribute to also apply to the arrow?
I'd also like to see optgroup styling made available for IE7.
Since only IE bothers with any IECCSS (IE conditional comments stylesheet) how about some sort of added support for throw IE's proprietary items inside?
<meta http-equiv="imagetoolbar" content="no" />
Or allowing some sort of clientside includes?
Anonymous
January 01, 2003
<select> now styles correctly... good.
<option disabled> still doesn't work... why not?
Take a break from developing all the proprietary technology that I can't use (because it's proprietary) and implement standards, please.
Anonymous
January 01, 2003
Talking about z-index; will IE7 fix the general issues with the z-index implementation as described on http://therealcrisp.xs4all.nl/meuk/IE-zindexbug.html and more in detail on http://www.aplus.co.yu/css/z-pos/ ?
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
This will be a great improvement, I always found this problem a frustrating one in IE.
Despite these additions being present in many other current browsers I'm really glad to see the MS developers enthusiasm for new IE features. I'm sure that it will eventually show in the quality of the release.
Anonymous
January 01, 2003
Please add type-ahead item selection
If a select item has items:
abc
aba
ccb
I should be able to focus on the control and type abc, and have it select the right item. This is so annoying in IE6 where it would end up selecting ccb
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
PatriotB,
You are correct. Bonus points for paying attention :)
The drop down part of the SELECT element does use a separate window as you'd expect so that it is fully visible when dropped down. The drop down is dismissed if you click away from it or move focus elsewhere as you'd expect in any Windows application.
Thanks
-Dave Massy
Anonymous
January 01, 2003
<meta http-equiv="imagetoolbar" content="no" />
@John: For what it's worth, the imagetoolbar was removed for IE7.
Anonymous
January 01, 2003
Several people have been reporting and demanding normal, standard support for the
- disabled attribute for optgroup
- disabled attribute for option
- label attribute for optgroup
- label attribute for option
- multiple attribute for select
- option defaultSelected is not supported by IE6
see
http://www.gtalbot.org/BrowserBugsSection/MSIE6Bugs/DefaultSelectedTrueOption.html
- objSelect.add(objOption, null) is not supported by MSIE 6
see
http://www.gtalbot.org/BrowserBugsSection/MSIE6Bugs/DefaultSelectedTrueOption.html
etc,etc,etc...
There are many bugs to fix in MSIE 6 regarding select objects.
Anonymous
January 01, 2003
Anything that makes the next version of IE more web standards compliant is a good thing. It's more important than tabs. Bravo!
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
Hi,
I have been using IE7 from the day it was released and am very happy with it. But lately im having problems with it when i access mail at yahoo. When ever i open a mail message in yahoo the browser just closes. This is happenning from the past 3 days. Has anyone else encountered this problem?
Any help in this matter is very appreciated.
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
"With current versions of Internet Explorer, it looks for certain meta http-equiv elements. However if that information is included as a proper HTTP header, it gets ignored."
@Jim: The only case I'm aware of where this is still true is the MSThemeCompatible tag. We should not have implemented this as a HTTP-EQUIV meta. Instead, we should have used META NAME=MSThemeCompatible, as we did for the DownloadOptions meta introduced in XPSP2.
If you know of other instances, I'll look into them.
Thanks!
Anonymous
January 01, 2003
This is good news, all I can say for now.
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
I'd like to see the keyboard navigation for the SELECT element improved, so typing out the full name of an option works properly. Currently, keyboard navigation only works on the first letter of an option, and hitting the letter repeatedly goes through the options.
Other browsers have a better implementation where typing the full word jumps directly there.
Although I haven't used the IE7 beta, I think this is a major drawback of accessibility in IE6.
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
Al Billings [MSFT]: "Game Kid, when I go to the link above in a current IE7 build, I don't see any boxes around the math symbols."
Not around, but in place of them, i.e. even if there's a Unicode font installed that IE can use, it will show boxes anyway unless explicitly chosen.
Thanks either way.
Matt Ryall: "I'd like to see the keyboard navigation for the SELECT element improved, so typing out the full name of an option works properly.[...]Although I haven't used the IE7 beta, I think this is a major drawback of accessibility in IE6."
IE7 sounds good, and I hope we'll actually be using it soon. Microsoft could use some input and error reports from more people who use the Internet. I doubt hiding your light will brighten it for long.
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
@gamekid: The symbols render correctly with no boxes.
@PatriotB: The documentation is really poorly formatted. The answer is that you want to click on the CONTENT link at the top of the NAME attribute article to see the values. Specifically, the options for DownloadOptions are:
<META NAME="DownloadOptions" CONTENT="noopen">
<META NAME="DownloadOptions" CONTENT="nosave">
If you use the first, downloads from the page containing the meta cannot be Run/Opened from the File Download dialog. For the second, downloads can only be Run/Opened.
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
As much as I want it to act like Firefox, what does the standard say about what should happen when users type?
Anonymous
January 01, 2003
I haven't memorised them completely yet ;) but I'm pretty sure that they don't speak to the issue. Something like that should be left to the implementation. I personally like firefox's behaviour better, but I don't think that the browsers need to be exactly the same, as long as they follow the standards.
Anonymous
January 01, 2003
To pick up on the side comments regarding font switching (as described in this Mozilla document: http://www.mozilla.org/projects/intl/fonts.html):
Font-fallback support did not work well in IE6. Many "lesser-used scripts" with currently inadequate font support rely on browser font switching to provide the missing glyphs, and alas IE6 is the ONLY major browser that cannot do this. (Makes me wonder whether Microsoft really wants those markets.) Web authors should be able to specify any font and have the missing glyphs supplemented by any other installed fonts that have support those code points. I hope IE7 will improve on this.
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
On Wednesday, January 18, 2006 4:11 AM - Kae Verens wrote
re Igor Abade's request for nested optgroups. The w3c specs specifically disallow nested optgroups. from the specs, "groups may not be nested".
http://www.w3.org/TR/html4/interact/forms.html#edef-OPTGROUP
However the said spec clearly states:
Note. Implementors are advised that future versions of HTML may extend the grouping mechanism to allow for nested groups (i.e., OPTGROUP elements may nest). This will allow authors to represent a richer hierarchy of choices.
So, it would be a great leap ahead if IE7 supoport for nested OptGroups.
Even better if the new SELECT tag could be rendered as a menu, in special when using the OptGroup it could be rendered as an hierarchical menus.
Just as the example in the specs.
Anonymous
January 01, 2003
@Eric - another example of a header that is honored in a <meta> tag but ignored in a real header is the Refresh header.
If a Refresh header is sent that is longer than 255 characters, it is ignored.
See http://matthew.vaneerde.com/http-refresh.asp
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
@<<Little is known about IE 7.0.>>
Proof positive that some people aren't reading the IEBlog. So far, we've posted about Antiphishing, Enhanced security, protected mode, SSL, IDN, and pretty much every major feature you'll see in IE7. And more detail will be forthcoming with the Q1 preview release.
@Maurits: The refresh length limit is an interesting finding, but at least this one is supported in the header parsing code. I'll file a bug.
Anonymous
January 01, 2003
Two more things to fix for <select> while you're at it:
* options don't support correctly (put two in a row and it becomes just one space)
* option doesn't support white-space:pre;
Those would be greatly appreciated. :)
Thanks,
Drew
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
Kyle the behavior you describe is in accordance with the spec.
As far as Javascript is concerned, op.value is whatever is in the value="..." attribute.
As far as HTML is concerned, if the value attribute is missing, then the CONTENTS of the option tag is submitted. (Quote from the HTML 4 spec: "If this attribute is
not set, the initial value [p.220] is set to the contents of the OPTION element")
Anonymous
January 01, 2003
It’s great to know we had worked on the right direction to improve user satisfaction! 8-)
My team worked on IE7 Font Linking to make IE7 smarter than IE6. For any character in Unicode BMP plane, even if web developer hasn’t assigned a font name or assigned a WRONG font name, IE7 will render it legibly as long as there is a Windows stock font that can shape it. This improvement will not only be seen for math symbols, but also for many other characters in Hebrew, Greek, Cyrillic, Latin Extended-B, IPA-Extenstions...
Anonymous
January 01, 2003
Please, please, stop mucking about with IE and just license someone else's rendering engine. It's going to take ages for you to fix half the CSS bugs. You should have started this process 5 years ago and it's too late now.
Please just buy Opera or something and bin IE. It is a daily nightmare for a web developer
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
How about the OBJECT tag, the select is one of two windowed controls, do you have any intention of tackling that element also?
Regards,
-Z
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
@Kyle - that's interesting, I hadn't thought of it that way.
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
>>the logical conclusion/deduction means that "later release" means:
MSIE 8 beta 1: will be released march 2010<<
Arithmetic error aside, I notice that you're conveniently omitting the entire history of IE before version 6, as well as IE6 for XPSP2, which introduced a significant number of features.
IE8 planning is already underway, and we appreciate the valuable feedback we've been receiving on what we should be working on, as well as the feedback we've received on IE7. Thanks!
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
There is a problem with select element on site wich using "DXImageTransform.Microsoft.Gradient" filter if user is scrolling down the page. For example look at http://www.letectvi.xf.cz/enu/boeing-777 on the select element on the right near "Show specification for:".
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
Im currently using the leaked Beta 2 (build 5299).
Suggestions:
- It should be possible to drag the url of the open tab to a new one, so you have two tabs with the same url.
Nice release!
Arjan
Anonymous
January 01, 2003
The comment has been removed
Anonymous
January 01, 2003
Are any of the most basic problems with DOM access of SELECT elements
expected to be fixed? Among these are:
var a = new Option('a','a'), b = new Option('b','b'),
s = document.createElement('select'),s2;
s.add(a,null);
s.add(b,null); // doesn't work in IE; IE expects, incorrectly, that
// the 2nd argument should be an index rather than
// a reference to an element.
// s.add(b,a); // should reverse the order of options; but even coded as
s.add(b,0); // this fails, (? because b already has a parentNode,
// and the add() method requires options to be
// parent-less
s2 = document.createElement('select');
s2.add(a); // should move the option from s to s2, but fails,
// presumably because a hasn't been removed from s yet?
// OK, then
s.removeChild(a);
s2.add(a); // still fails; when you remove a node from its parent,
// IE apparently fabricates a #document-fragment node
// to act as a "surrogate parent", instead of setting
// a.parentNode = null. This prevents(?) s2.add from
// working correctly.
There are a whole slew of issues like this, many that are more general,
that get in the way of simple SELECT-handling code. Is there any hope?
Anonymous
January 01, 2003
This is great! Now how about an HTML 4 feature that is still not supported: implicit association of <label>s to controls?
Anonymous
January 01, 2003
Hello. Apparently still an issue with IE 7.0.5112.0 (Beta 1), using .Net 1.1 to render a dhtml menu over an IFrame containing an asp.Net DropDownList control
Anonymous
January 01, 2003
Hi Chameleon,
Sorry if it wasn't clear from this post but the new Select element work has only been added to IE7 since beta 1. You can expect to see this work in the next preview build.
Thanks
-Dave Massy [MSFT]
Anonymous
January 01, 2003
I was wondering if this new select will support title tags for each option tag. In IE6 after resizing the select to a smaller size the options are cut off. In other browsers you can then add a title tag so that a tooltip will display the option's full title on mouseover. I would assume this would be part of making it a standard HTML control, but I wanted to check and make sure.
Anonymous
January 01, 2003
PingBack from http://girtby.net/archives/2006/01/31/bloggable-mass/
Anonymous
January 01, 2003
PingBack from http://sudrien.net/technical/ccmock/sarissa/
Anonymous
January 31, 2006
The comment has been removed
Anonymous
February 01, 2006
The comment has been removed
Anonymous
February 02, 2006
Great news this. This also makes life much easier for detecting clicks on SELECT objects. Our product records internet macros in Internet Explorer and with the old windowed control it gets the mouse event before the document, so you couldn't use elementFromPoint using the mouse coords. We had to use a rather convoluted process of working out which SELECT object was clicked on. With IE7 it works just like any other DHTML object. Much easier! Thanks.
Anonymous
February 02, 2006
@Galeno in this preview it looks like "Ctrl +" zooms in, "Ctrl -" zooms out, and "Ctrl *" resets the zoom.
I'm glad to see select now observes z-order. I'm tired of having to place an IFRAME behind any absolute DIV tags that I want to show above a SELECT element. I have yet to experiment, but does the new select play well with filters like Alpha?
Anonymous
February 12, 2006
The comment has been removed
Anonymous
February 25, 2006
The comment has been removed
Anonymous
March 04, 2006
PingBack from http://vistadev.wordpress.com/2006/03/04/ie7-more-selective/
Anonymous
March 04, 2006
PingBack from http://vistadev.wordpress.com/2006/03/04/modifying-uac-policies/
Anonymous
April 06, 2006
PingBack from http://www.sitening.com/blog/2006/03/29/create-a-modal-dialog-using-css-and-javascript/
Anonymous
May 30, 2006
PingBack from http://www.acheron.org/darryl/?p=81
Anonymous
October 10, 2006
PingBack from http://www.jochemprins.com/2006/10/10/internet-explorer-7-to-be-released-this-month/
Anonymous
November 07, 2006
PingBack from http://xhtmlforum.de/42838-form-tag-steht-immer-im-vordergrund.html#post313965
Anonymous
November 14, 2006
PingBack from http://jblack.wordpress.com/2006/11/15/modal-dialog-for-all/
Anonymous
November 28, 2006
PingBack from http://girtby.net/articles/2006/01/31/bloggable-mass
Anonymous
April 25, 2007
PingBack from http://webjournl.wordpress.com/2007/04/25/ie-overlays-the-select-boxes-on-top-of-divs/
Anonymous
May 25, 2007
Negli ultimi mesi sono stato impegnato (tra le altre cose :-)) su un progetto piuttosto articolato basato
Anonymous
July 06, 2007
PingBack from http://www.programmerstalk.net/thread853.html#post2289
Anonymous
August 12, 2007
PingBack from http://krisgale.com/three-things-every-web-developer-should-know-about-internet-explorer-7/
Anonymous
August 14, 2007
PingBack from http://www.codingstyle.fr/2007/08/15/pour-en-finir-avec-les-problemes-de-z-index/
Anonymous
December 03, 2007
PingBack from http://thinkweb2.com/projects/prototype/2007/12/03/protomenu-gets-facelift/
Anonymous
December 15, 2007
PingBack from http://www.glagla.org/weblog/2007/03/02/internet-explorer-reste-un-cauchemar-pour-les-developpeurs-web/
Anonymous
January 14, 2008
PingBack from http://www.fatihhayrioglu.com/?p=446
Anonymous
January 26, 2008
PingBack from http://softwareinformation.247blogging.info/ieblog-for-the-select-few/
Anonymous
July 01, 2008
PingBack from http://lucaswebsite.hostedwith.us/ieoptionelementfontsize.html
Anonymous
January 01, 2009
PingBack from http://blog.inspired.no/fix-for-the-fix-202
Anonymous
January 22, 2009
PingBack from http://www.hilpers.nl/152227-dropdown-menu-mbv-form-option/3
Anonymous
March 02, 2009
症状:
如果你采用了ajax来动态填充内容,在填充select的时候,页面上有两个select并排,如果填充的内容长度超过默认的长度,则在IE7下不会自动扩展后面一个select框的位置。如图所示第...
Anonymous
April 28, 2009
PingBack from http://blog.davidemontersino.com/2009/04/ie6-css-bug-dropdown-menu-z-index-and-form-elementsie6-css-bug-dropdown-menu-z-index-e-elementi-dei-form/
Anonymous
May 29, 2009
PingBack from http://paidsurveyshub.info/story.php?title=ieblog-for-the-select-few
Anonymous
June 08, 2009
PingBack from http://jointpainreliefs.info/story.php?id=2356
Anonymous
June 13, 2009
PingBack from http://homelightingconcept.info/story.php?id=3592
Anonymous
June 15, 2009
PingBack from http://debtsolutionsnow.info/story.php?id=12312
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign in