Visual Studio and .NET Framework Home
Z-index issue when a web page is launched using the .NET Web Browser Control (WBC) inside an Excel 2007 Document Level Customization.
Abhishek - Oracle
as Won't Fix
10/24/2008 7:24:16 PM
User(s) can reproduce this bug
Windows XP --> Windows XP 2002 (SP2)
Excel version --> Microsoft Office Professional Edition 2007
.Net version --> Microsoft .NET Framework 3.5
Programming Language--> C#
IDE --> Visual Studio Team Suite 2008
Microsoft Visual Studio Tools for Microsoft Office Runtime --> VSTO 3.0
When a web page is launched from an Excel 2007 document level solution using the .NET Web Browser Control (WBC), the Z-index of the rendered page is not correct.
Select controls (like html drop-down lists) are still visible even after disabling (graying out) the whole page.
This does not happen when the WBC is used inside a regular Windows Form Application. In this case, the page behaves as expected and the drop-down lists are NOT active.
I have attached two applications and a document in "ExcelWebBrowserTest.zip". The problem happens only in "ExcelWebBrowserTest.zip". But, "WBC_NO_EXCEL.zip" can be run to see the expected behavior.
Visual Studio 2008 (All Products and Editions)
Windows XP Professional
Operating System Language
Steps to Reproduce
Create a document level customization using Excel 2007 and Visual Studio Team Suite 2008. Add a form containing the WebBrowserControl (name the class say WBC). Create a simple textbox and a button on the excel worksheet from the toolbox. In the button click eventhandler, create an instance of the WBC, set the WBC.Navigate(url)from the textbox entry. The textbox entry should contain the address of the page created below. Use the form.showdialog() or form.show() methods to open up the web page.
For the html page, create a simple HTML page which shows a page with HTML selects and then a div over it to "gray out" the page.
When a web page is launched from an Excel 2007 document level solution using the .NET Web Browser Control (WBC), the Z-index of the rendered page is not correct. Select controls (html drop-down lists) are still visible even after disabling (graying out) the whole page.
This does not happen when the Web Browser Control is used inside a regular Windows Form Application. In this case, the page behaves as expected and the drop-down lists are NOT active.
The same should happen when launched from an Office customization.
TAP Code (if applicable)
You can indicate your satisfaction with how Microsoft handled this issue by completing this quick
3 question survey
to post a comment.
Please enter a comment.
on 11/5/2008 at 8:04 PM
Thanks for your feedback on the .NET Framework!
Customer feedback is a critical part of a successful, impactful product release. Unfortunately another part is the reality of schedules and the need to get the bits into production. We have evaluated your suggestion and it does not meet the criteria to be addressed in this release. This evaluation is carefully done and considers many aspects including fix cost, breaking changes, globalization, performance, etc.
Many customers have found it useful to discuss issues like this in the forums (http://forums.microsoft.com/msdn/default.aspx?siteid=1) where Microsoft and other members of the community can suggest workarounds.
Before we even begin work on the next release of the NET Framework release where we can make changes like this one we will devote time to addressing the top issues/suggestion (in terms of number of votes, lack of workarounds, etc). So please do continue to vote for this item if it is causing issues.
Please keep the feedbacks coming.
on 11/5/2008 at 2:16 AM
We were able to reproduce the issue you are seeing. We are escalating this issue to the product unit who works on that specific feature area. The product team will review this issue and make a decision on whether they will fix it or not for the next release
on 10/29/2008 at 1:56 AM
Thanks for reporting the issue.
In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.
It may help if you provide us with:
a) a zipped project file
b) a screenshot about the problem
It would be greatly appreciated if you could provide us with that information as quickly as possible. If we do not hear back from you within 7 days, we will close this issue
Thanks again for your efforts and we look forward to hearing from you.
Visual Studio Product Team
on 10/28/2008 at 2:04 AM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com/)
to post a workaround.
Please enter a workaround.
© 2014 Microsoft