You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2013/07/25 00:11:48 UTC

[jira] [Commented] (TAP5-2106) Tapestry incorrectly rewrites CSS urls in a variety of cases

    [ https://issues.apache.org/jira/browse/TAP5-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718908#comment-13718908 ] 

Howard M. Lewis Ship commented on TAP5-2106:
--------------------------------------------

I just beefed up the regular expression to handle Dimitri's case.

I won't be fixing the situation where url()'s in comments are being parsed; I looked for an off-the-shelf solution (a CSS parser that would could be used to stream most content unchanged, but provide a hook to modify urls).  I haven't found one with with a compatible license.

Please add a new issue to address the parsing of comments, if this is an issue. Essentially, you have the power to remove the offending URLs from the comments of your CSS files, so this is not a big concern I'm afraid.
                
> Tapestry incorrectly rewrites CSS urls in a variety of cases
> ------------------------------------------------------------
>
>                 Key: TAP5-2106
>                 URL: https://issues.apache.org/jira/browse/TAP5-2106
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Michael Gentry
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.4
>
>
> T5.4 doesn't handle CSS URLs in this format:
>     behavior: url(#default#VML);
> It fails upon re-writing the URL.  This may also impact 5.3.x (didn't evaluate that version).
> Related user-list e-mail thread:
> http://mail-archives.apache.org/mod_mbox/tapestry-users/201304.mbox/%3cCAA-upzqY4WNyfpeck1HxVyMxH=8jE2Bt96Ocx6b7oak+HmBpLQ@mail.gmail.com%3e

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira