Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 458291 - [CSS] support styling exception with 'initial' properties
Summary: [CSS] support styling exception with 'initial' properties
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.5   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Stefan Winkler CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-23 13:47 EST by Stefan Winkler CLA
Modified: 2020-03-05 16:40 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Winkler CLA 2015-01-23 13:47:20 EST 
To simplify the dark theme (see Bug 431845) it would be great to have a catch-all rule like this

* {
  background-color: ...
  color: ...
}

The problem is that with the current implementation, this catch-all rule also catches StyledText (and thus, e.g., the JDT editor and other editors with syntax-highlighting).

In order to specify exceptions, we want to implement the CSS3 keyword 'initial' which tells the CSS Engine to not style the respective property but to use the default value.

Then we can use the catch-all rule above and then have a rule to restore default behavior for StyledText:

StyledText {
  background-color: initial;
  color: initial;
}
Comment 1 Lars Vogel CLA 2015-02-16 14:24:29 EST 
Is this still useful for the simplification of the dark theme?
Comment 2 Lars Vogel CLA 2015-02-26 16:43:06 EST 
Stefan, any update here. M6 is our last milestone where we can work on "API".
Comment 3 Eclipse Genie CLA 2020-03-05 16:40:34 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.