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.

Bug 121847 - css color editing broken
Summary: css color editing broken
Status: RESOLVED WONTFIX
Alias: None
Product: obsolete
Classification: Unclassified
Component: languages (show other bugs)
Version: 6.x
Hardware: Macintosh All
: P3 blocker with 5 votes (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-13 18:37 UTC by jerrett
Modified: 2008-07-30 09:20 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
broken jsp syntax highlighting after editing css files (37.17 KB, image/png)
2008-06-18 13:08 UTC, alexeym
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jerrett 2007-11-13 18:37:58 UTC
tested in todays build (5202)


editing CSS is broken in that I can not change some of the colors, notable the keyword color - it allows me to change it
in the color editing UI, but when i change it only part of the preview changes, the rest stays dark blue (default color).


Opening a file will  show the proper colors for a second or two, and the revert.


the two colors that seem to be the most obvious are the keyword color (dark blue) and the identifier color (dark green)
Comment 1 Torbjorn Norbye 2007-11-13 21:20:54 UTC
I've seen the same problem and I -just- realized what the problem is.

At the -lexical- level, the CSS colors are assigned the lexical colors assigned to keys and values.

However, the Schliemann CSS parser then kicks in and -changes- the colors according to its own hardcoded colors in CSS.nbs:

COLOR:key: {
    color_name: "css_key";
    default_coloring: "keyword";
    foreground_color:"blue";
} 

This doesn't work well with themes. Is it really necessary to set the colors here? I think it should instead be using
logical color names (for example "mod-unused" for unused variables, "mark-occurrences" for occurrences highlighting etc)
such that this works with the various themes.
Comment 2 jerrett 2007-11-15 21:57:20 UTC
there appears to be a similar problem with js color highlighting - 


var foo = "asfs";
x = /foo/;


both the regex and the variable name show up dark green, even though they are set to white and yellow in the color options.
Comment 3 Jan Jancura 2008-01-16 18:25:28 UTC
We will look at it.
Comment 4 alexeym 2008-05-01 03:08:25 UTC
Similar problem exists with diff .patch files.

I can't change colors for added/removed lines and headers.
Comment 5 Martin Krauskopf 2008-05-07 17:34:09 UTC
More users reports this problem on users and ruby-users forum.
Comment 6 alexeym 2008-06-18 13:04:48 UTC
In netbeans 6.1 after editing css files highlighting becomes broken in css and jsp files.
Comment 7 alexeym 2008-06-18 13:08:05 UTC
Created attachment 62989 [details]
broken jsp syntax highlighting after editing css files
Comment 8 Jan Jancura 2008-07-30 09:20:37 UTC
languages/css module has been removed from NetBeans build.