WPF Ribbon Window: The border is too thin - by omjbe

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 775972 Comments
Status Closed Workarounds
Type Bug Repros 13
Opened 1/7/2013 7:30:41 AM
Access Restriction Public


The WPF 4.5 Ribbon implementation comes with some visual issues. These issues were not seen with the “Microsoft Ribbon for WPF October 2010” (http://www.microsoft.com/en-us/download/details.aspx?id=11877) implementation.
* The window content (client area) is cropped when the window is in Maximized mode.
* The window border is too thin.
* QuickAccessToolbar does not have enough “margin” to the top.
* The window title is blurry and does not have enough “margin” to the top.
Sign in to post a comment.
Posted by Wouter Staelens on 9/8/2015 at 7:34 AM
Vote on Uservoice page:
Posted by dd3 on 6/11/2015 at 6:19 AM
I can not believe this was closed! I bet Ribbon's are ment to die and therefor no fix is provided.
Posted by James079 on 4/28/2015 at 4:50 AM
What a joke. Higher priority issues ? Really ?
Posted by omjbe on 3/1/2015 at 1:23 PM
Is this a joke? After mentioning to investigate this bug in your blog post “The Roadmap for WPF” I was sure that this gets fixed.

See chapter: “We take your feedback to heart!” @ http://blogs.msdn.com/b/dotnet/archive/2014/11/12/the-roadmap-for-wpf.aspx
Posted by Sachin [MSFT] on 2/27/2015 at 12:26 PM
The WPF team has reviewed this issue and is unable to address it at this time as we are working on higher priority issues for the WPF community. We thank you for the feedback and may consider this issue again while triaging issues for a future version of WPF.     – WPF team
Posted by Akhil Garg on 7/10/2014 at 8:55 PM
This issue is coming with Win7 Aero themes .Title bar is getting cut off.
Posted by omjbe on 6/10/2014 at 11:00 PM
Please do not close bugs without even providing a workaround. I have not found a “good” workaround so far. I believe this issue can only be fixed in WPF itself.
Posted by omjbe on 5/4/2014 at 11:58 PM
Unfortunately, we have not found an acceptable workaround. We have investigated some of them but they all come with other negative side-effects. Until now we hope that Microsoft is going to fix this bug in a future .NET Framework version.
Posted by sparticus1701 on 5/2/2014 at 8:41 AM

Were you able to get any of the workarounds working, or have you resolved this issue another way? I am in the same situation.
Posted by omjbe on 10/25/2013 at 4:18 AM
Fluent ribbon or any other 3rd party library is not an option for us. Our applications have a lifetime of more than 10 years. Such libraries are seldom maintained that long and we do not have the time to do it ourselves. Therefore, we stick to the official .NET Framework API which is supported for a long time.
Posted by Staeff on 10/25/2013 at 3:21 AM
Just use Fluent ribbon library, it's much more convenient to use and also has Office 2013 styles. fluent.codeplex.com
Posted by omjbe on 10/24/2013 at 7:33 AM
Please review this issue again because none of the workarounds seems to work. This is a very serious issue for us.
Posted by Chipalo [MSFT] on 3/29/2013 at 11:22 AM
The WPF team has recently reviewed this issue and will not be addressing this issue as at this time the team is focusing on the bugs impacting the highest number of WPF developers. If you believe that this was resolved in error, please reactivate this bug with any necessary supporting details.

We appreciate the feedback. However, this issue will not be addressed in the next version of WPF. Thank you.
–WPF Team.
Posted by Microsoft on 1/7/2013 at 6:29 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 1/7/2013 at 7:50 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)