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.
use this code: ------------------- table { background-position:center top; } ------------------ the line is yellow underlined with a warning, but the code is correct P.S. try to switch center, top order to ------------------ background-position:top center ; ------------------ warning disapears, but possitions are separated by || in CSS values grammer so there should be no influence of the order
reproducible, added currently failing unit test PropertyModelTest.testBackroundPositionOrder()
General comment: adding PropertyModelTest.testBackroundPositionOrder() is good but we should annotate these tests somehow and exclude them from regular run or something. I run tests before and after any change to verify that I have not broken anything else. And if a test fails I have no idea to know whether it is by designed or not.
You are completely right. I just remember it, doable for a limited number of tests. Is there such mechanism Davide?
None I would not of. I thought we could use @RandomelyFails from org.nb.junit but its purpose is different. I would probably comment out (or "if (true) return") the test until the issue is fixed. And fixing issue should put the test back. Just an idea. What do you think?
It looks we could use junit4's @Ignore annotation so the test could look like: @Test @Ignore("issue XXXX") public void jindrasCase() { ... } The problem seems to be that junit switches to some pre 4 compatibility mode if the test class extends TestCase. In such case the annotation are not processed. If we do not extend the NbTestCase then some of the used nbjunit functionality misses.
already fixed