[
https://issues.apache.org/jira/browse/TAP5-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645685#comment-13645685
]
Michael Gentry commented on TAP5-2106:
--------------------------------------
Possibly also related. Using a local copy of Font Awesome (under the WEB-INF
directory) gives this exception:
org.apache.tapestry5.ioc.internal.OperationException
Unable to locate asset
'context:3rdParty/font-awesome/font/fontawesome-webfont.eot?v=3.0.1' (the file
does not exist).
Handling page render request for page Index
Rewriting relative URLs in
context:3rdParty/font-awesome/css/font-awesome.min.css
The Font Awesome CSS can be found here:
http://fortawesome.github.io/Font-Awesome/assets/css/font-awesome.css
And the re-writing of the relative URL is being tripped up by the @font-face at
the top:
@font-face {
font-family: 'FontAwesome';
src: url('../font/fontawesome-webfont.eot?v=3.0.1');
src: url('../font/fontawesome-webfont.eot?#iefix&v=3.0.1')
format('embedded-opentype'),
url('../font/fontawesome-webfont.woff?v=3.0.1') format('woff'),
url('../font/fontawesome-webfont.ttf?v=3.0.1') format('truetype');
font-weight: normal;
font-style: normal;
}
When the "?v=3.0.1" was removed it worked (as in progressing further to fail at
the #iefix...).
> T5.4 + #default#VML CSS URLs
> ----------------------------
>
> 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
>
> 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+hmb...@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