tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-797) Using "tapestry.combine-scripts" with an EmptyClientInfrastructure still adds an empty JavaScript file
Date Thu, 25 Jul 2013 19:41:50 GMT

     [ https://issues.apache.org/jira/browse/TAP5-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship closed TAP5-797.
-------------------------------------

    Resolution: Won't Fix

Time has moved on; all the asset infrastructure has changed repeatedly since 5.1.
                
> Using "tapestry.combine-scripts" with an EmptyClientInfrastructure still adds an empty
JavaScript file
> ------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-797
>                 URL: https://issues.apache.org/jira/browse/TAP5-797
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Carl Crowder
>            Priority: Minor
>              Labels: bulk-close-candidate
>         Attachments: check_no_script_tag_if_no_scripts.diff
>
>
> If you have "tapestry.combine-scripts" set to true, and override the ClientInfrastructure
service to not add any assets, the DocumentLinkerImpl still inserts a SCRIPT tag into the
document. The JavaScript it generates is empty except for a call to the Tapestry JavaScript
object, which isn't part of the page anyway as no other JavaScript has been loaded.
> This a) causes a JavaScript error and b) adds unecessary HTTP requests.

--
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

Mime
View raw message