| Summary: | [CSS] CSS parsing exceptions are silently tossed | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Brian de Alwis <bsd> |
| Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | psuzzi |
| Version: | 4.5 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | stalebug | ||
Eclipse can be styled via CSS. Detecting CSS bugs is quite important. Currently, users can detect most of CSS errors only by starting their RCP applications with the -consoleLog parameter. As an example, see: https://bugs.eclipse.org/bugs/show_bug.cgi?id=500402#c6 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. |
Consider the following CSS fragment: IEclipsePreferences#org-eclipse-ui-workbench { preferences: } Text { foreground: white; } The 'preferences:' property is incomplete and although the underlying CSS parser reports an error, we currently do not provide an error handler and Batik’s default error handler only outputs fatal errors to stdout. We should configure E4 CSS to provide an error handler. I haven't done this previously as we don’t have a clear error-reporting strategy and we were trying to avoid pulling in org.eclipse.core.runtime. The best way to discover these exceptions in the interim is to place an exception breakpoint on org.w3c.css.sac.CSSParseException.