OK, thanks! And sorry, a colleague just reminded me of bugs.openjdk.java.net <http://bugs.openjdk.java.net/>, I was obviously searching in the wrong bug tracker.. You already reported it: https://bugs.openjdk.java.net/browse/JDK-8093583
> On 18 Aug 2015, at 17:03, Hervé Girod <herve.gi...@gmail.com> wrote: > > I think it has been fixed for u60. > > Sent from my iPhone > >> On Aug 18, 2015, at 16:43, Thomas Meyer <meyer...@gmail.com> wrote: >> >> Hi, >> >> I’m using @import statements to spilt up my CSS code into multiple files in >> subdirectories. All imports are listed in one base css file: >> >> base.css: >> @import “sub/a.css" >> @import “sub/b.css" >> >> This usage was working fine in JDK 1.8.0_31. Since JDK 1.8.0_45 it’s broken: >> “sub/b.css" is resolved relative to “sub/a.css” leading to errors such as >> this one (notice the double-“/sub"): >> >> com.sun.javafx.css.parser.CSSParser handleImport >> WARNING: CSS Error parsing >> file:/myproject/build/classes/main/styles/sub/sub/b.css: Could not import >> “sub/b.css” >> >> Information on the support for @import is sparse on the CSS-ref. Is this >> usage discouraged? What others use cases does it serve / how are you using >> the @import statement? >> >> Best wishes, Thomas.
