Hello Jean,

If you would like to change the message, you can simply change in TextSettings properties  (child WebCombo).

e.g 

 <TextSettings ParentEmptyPromptText="{0} value should be selected" />

However, you could not change the style of its style because it is browser alert.
I suggest you to use WebDialogBox as the workaround. In this case, you will need to use "ShowEmptyResult" value in LinkSettings>>ParentEmptyAction properties.

This value would ignore the alert or any messages. Then, show WebDialogBox in OnShowDropDown clientside events. By using WebDialogBox as the message, you can configure freely your message style.
For further information, please see Yudi's reply. He posted a simple sample about how to use WebDialogBox for your scenario.

Regards,
Handy

Hello Nico,

You can use custom CSS to configure WebCombo style without no issue. But, there are some major styles that could not be changed due to design or function purpose. Those are very basic style which should not be changed.
E.g some of the styles are used for properties function purpose which can only work in XHTML doctype or etc.

However, WebCombo still allow user to configure its style freely, except some basics styles. You can see that we provide some WebCombo style sample in our WebCombo sample. 
For easy customization, please set UseDefaultStyle as false. Then, you can customize WebCombo style with your own custom CSS. Below are the list of properties that allow user to customize its style.

• HeaderStyle
• DropDownStyle
• TextBoxStyle
• ResultFrameStyle
• ColumnStyle
• FrameStyle
• MoreButtonStyle
• StatusBoxStyle
• ResultBoxStyle
• RowStyle
• SelectedRowStyle

About the last differences display between IE7 and IE8, that is a browser behaviour.
In IE8, some properties need to be turned off manually.
For this case, please try to turn off AllowFloatingText under LayoutSettings properties.
You can see that there is no differences between the layout now.

Regards,
Handy

Hello Doug,

Ok, I will discuss this to our development team. But as far I know, even though the log is looking into subdirectory, as long it can open the resources images, then the issue should be not happened.
There are some issues when the images could not be shown.
E.g under in IIS7.
To resolve this issue, normally we moved the resources handler into <system.webServer> in web.config.

The web.config will look like following:

<system.webServer>
   <validation validateIntegratedModeConfiguration="false"/>
   <handlers>
      <add name="ISCoverFlow.axd_GET" path="ISCoverFlow.axd" verb="GET" type="ISNet.WebUI.Silverlight.WebAqua.WebCoverFlowRequestHandler, ISNet.WebUI.Silverlight.WebAqua" preCondition="integratedMode"/>
      <add name="ISChart.axd_GET, POST" path="ISChart.axd" verb="GET, POST" type="ISNet.WebUI.WebGrid.Chart.ChartRequestHandler, ISNet.WebUI.WebGrid" preCondition="integratedMode"/>
      <add name="ISRes.axd_GET" path="ISRes.axd" verb="GET" type="ISNet.WebUI.WebResourceHandler, ISNet.WebUI, Version=3.0.5000.1, Culture=neutral, PublicKeyToken=b1f2a8511635667a" preCondition="integratedMode"/>
      <add name="WebFileUploaderHttpHandler.axd_GET" path="WebFileUploaderHttpHandler.axd" verb="GET" type="ISNet.WebUI.WebTextEditor.WebFileUploaderHttpHandler, ISNet.WebUI.WebTextEditor" preCondition="integratedMode"/>
      <add name="ISScheduler.axd_GET" path="ISScheduler.axd" verb="GET" type="ISNet.WebUI.WebScheduler.WebSchedulerRequestHandler, ISNet.WebUI.WebScheduler" preCondition="integratedMode"/>
   </handlers>
   <modules>
      <add name="WebFileUploaderHttpModule_GET" preCondition="managedHandler" type="ISNet.WebUI.WebTextEditor.WebFileUploaderHttpModule, ISNet.WebUI.WebTextEditor" />
   </modules>
</system.webServer>                     

Regards,
Handy

Hello Doug,

I can run the sample fine even in sub directory. Please let me know if your current project is http or FileSystem. 
Also, Do you use SmartWebResources for your project? For more information, please send your web.config. Maybe some images path is set incorrectly within web.config.

Regards,
Handy

Hello Eric,

Regarding your first issue, I do find the workaround. Please see the modified sample. 
I moved some of your code in some proper events. It seems the errors persist because you used them in unproper event. 

About unmoved slider issue, I suspect that the ajax request especially Asynchronus Postback caused this issue. I am still not able to narrow the main cause.
If I add a simple WebGrid Paging and do some PostBack, the slider works well.
Perhaps, you can help us to find the cause because you are more familiar with the scenario.

Regards,
Handy