jahaziel17 / wro4j

Automatically exported from code.google.com/p/wro4j
0 stars 0 forks source link

Rhino Less CSS processor breaks on // in a string, eg http://example.com #703

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
## What steps will reproduce the problem?

Create a LESS file like this

    .foo:after {
        content: "Go to http://example.com/";
    }    

## What is the expected output? What do you see instead?

Should see the exact same output in CSS. Instead, this error is thrown

    Reason: Could not execute the script because: 
    {
      "type": "Parse",
      "message": "Syntax Error on line 37",
      "index": 728.0,
      "filename": null,
      "line": 37.0,
      "column": 4.0,
      "extract": [
        ".foo:after {",
        "    content: \"Go to http:",
        "}"
      ]
    }

## What version of the product are you using? On what operating system?

1.6.3 on Linux (Ubuntu 12.04 64 bit)

Original issue reported on code.google.com by gnoodl on 10 Apr 2013 at 1:01

GoogleCodeExporter commented 8 years ago
I'm guessing this has something to do with the comment stripper

Original comment by gnoodl on 10 Apr 2013 at 1:07

GoogleCodeExporter commented 8 years ago
An even more common test case is

    .foo {
        background-image: url(http://example.com/foo.png);
    }

Original comment by gnoodl on 10 Apr 2013 at 1:09

GoogleCodeExporter commented 8 years ago

Original comment by alex.obj...@gmail.com on 10 Apr 2013 at 9:00

GoogleCodeExporter commented 8 years ago
Could you provide the list of all processors used in your test-case?

Original comment by alex.obj...@gmail.com on 11 Apr 2013 at 4:22

GoogleCodeExporter commented 8 years ago
We use the following in wro.properties

    preProcessors=cssImport.less,rhinoLessCss.less,semicolonAppender
    postProcessors=cssMinJawr,jsMin

I see the issue in both stand-alone less files as well as imported ones

Original comment by gnoodl on 11 Apr 2013 at 11:03

GoogleCodeExporter commented 8 years ago
Fixed in branch 1.6.x

Original comment by alex.obj...@gmail.com on 18 Apr 2013 at 11:53

GoogleCodeExporter commented 8 years ago

Original comment by alex.obj...@gmail.com on 8 Jun 2013 at 9:43