Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#1 Syntax highlighting doesn't respond to profile change

Release_0.1.0
closed-fixed
CSS Support (3)
5
2004-02-16
2004-02-11
Christopher Lenz
No

Syntax highlighting of known properties and at-keywords doesn't
change when a different profile is selected.

To reproduce, make sure the default profile is set to "CSS Level 2",
and isn't overridden for the project or file. Then create a test CSS
file with the content:

@media screen {
h1 { text-shadow: 3px 3px 2px }
}

Both "@media" and "text-shadow" should be highlighted. Save and
close the test file, and change the default profile to "CSS Level 1".
After reopening the test CSS file the highlighting has not changed,
even though neither the @media at-keyword nor the text-shadow
property are defined for CSS level 1.

Discussion

  • Logged In: YES
    user_id=10889

    This is harder than I thought at first, because the profile can be set on a
    per-project or per-file basis, but the CSS text tools and thus the syntax
    highlighting is shared globally.

     
    • status: open --> open-accepted
     
  • Logged In: YES
    user_id=10889

    This is now fixed, but only for changes to the default
    profile. Need to investigate why changes to the profile set
    on a project- or resource-basis are not reflected.

     
  • Logged In: YES
    user_id=10889

    Now also fixed for profile settings on a project- or
    resource-basis.

     
    • status: open-accepted --> closed-fixed
     
    • milestone: --> Release_0.1.0