Search

"Add existing class" from DOM viewer doesn't see all available CSS classes by skills0

Closed
as By Design Help for as By Design

0
0
Sign in
 to vote
Type: Bug
ID: 746976
Opened: 6/6/2012 7:31:22 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
When editing a Metro html page, the only available CSS classes when using the "Add existing class" context menu are classes in a directly linked css file. There should be a way to see all the classes available to the page, even if there is an extra click to get to them. Or there should be a setting to turn this on and off.

For instance, I can't see any of the styles defined in the default WinJS themes (ui-light.css, ui-dark.css). Can't see styles linked in a top-level page when using navigation. Can't see styles linked in the parent page when using a WinJS.UI.HtmlControl.

This renders the whole prospect of defining layouts in Blend rather useless for anything other than simple scenarios. The whole point of CSS is the cascading/inheritance nature of the way styles are defined and referenced. It doesn't support a DRY pattern when working with CSS.

This is actuall in the Blend for Microsoft Visual Studio 2012 RC, Version 5.0.30514.0.
Details (expand)

Product Version?

 

Blend for Visual Studio 11 Beta

Language?

JS

Issue Type?

Bug

Repro Steps? (N/A for Suggestion)

 
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 6/20/2012 at 3:37 PM
I very much agree that we want our tools to work towards an elegant and clutter-free solution. To clarify, you are still referring to showing all defined class names coming from default WinJS themes in the "add existing class" list? Is there another aspect to styling in Blend that you feel would help minimize the number of classes/ids that you create?

Thanks,
Michelle
Posted by skills0 on 6/20/2012 at 9:12 AM
I totally understand the visual clutter concern. But it would still be nice to have it as an option (like a command sequence to see it). There are so many styles defined in the default themes that often it is not necessary to create new styles. I think the tooling should lead the user in the direction of defining the bare minimum number of styles necessary for the design to work. This reduces clutter in the actual solution, often leads to more elegant design and CSS structure and makes maintaining the app easier.

As far as the other question, I was thinking from the wrong direction. The parent page should be able to see the styles of the child (in the HtmlControl), but not vice versa since the child has no default notion of what its parent might be. So this is working correctly.
Posted by Microsoft on 6/20/2012 at 8:55 AM
Hi skills0,

Thanks again for your feedback. We did indeed consider including all available classes from the default WinJS themes in the "Add existing class" list, but due to visual clutter and performance reasons, we chose not to do so. I am therefore going to resolve this issue as "By Design".

With regard to your concern about seeing styles from top-level pages when using an HtmlControl, can you provide some more specific repro steps here? From a top-level page containing an HtmlControl, I am able to see both the top-level page's styles and the styles defined in the referenced HtmlControl in Blend.

Thanks,
Michelle
Blend for Visual Studio
Posted by Microsoft on 6/11/2012 at 2:40 PM
Hi skills0,

Thanks for your feedback! We are taking a look and will get back to you soon.

Thanks,
Michelle Rosenthal
Blend for Visual Studio
Sign in to post a workaround.
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement