This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: | Basic property sheets for visually editing SASS files | ||
|---|---|---|---|
| Product: | web | Reporter: | Petr Jiricka <pjiricka> |
| Component: | CSS Visual Tools | Assignee: | Jan Stola <jstola> |
| Status: | NEW --- | ||
| Severity: | normal | CC: | dkonecny, mfukala |
| Priority: | P2 | ||
| Version: | 7.4 | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
| Bug Depends on: | 235088 | ||
| Bug Blocks: | 235151 | ||
|
Description
Petr Jiricka
2013-05-09 09:09:11 UTC
This issue requests basic support for SASS property sheets. Once that's implemented it should be considered to expand upon this and provide some additional features taking advantage of basic SASS file semantics. See for example issue 233501 and attached test case. When "A link" is inspected in the testscase the first applied style is a:visited which is defined in a SASS file as
a:visited {
@include oj-link-visited;
}
It should be simple to find oj-link-visited SASS mixin which is defined as
@mixin oj-link-visited {
color: $linkTextColorVisited; // todo: lightness thing
}
and populate properties in Applied Styles window as:
color: $linkTextColorVisited
$linkTextColorVisited: #86defb
Ideally user would also get information about where the properties are declared so that they can navigate to the file, eg:
color: $linkTextColorVisited (_oj.alta.mixins.tags.css:46)
$linkTextColorVisited: #86defb (_t1-settings.scss:101)
Note: as I mentioned in issue 233501#c3 the variable $linkTextColorVisited is defined in 3 different files and in theory it should be possible to figure out in runtime which declaration had the precedence. But it may not. :-)
Something to consider.
|