Add ability to control where Ajax-injected CSS links are placed
---------------------------------------------------------------
Key: TAP5-1708
URL: https://issues.apache.org/jira/browse/TAP5-1708
Project: Tapestry 5
Issue Type: New Feature
Components: tapestry-core
Affects Versions: 5.3
Reporter: Howard M. Lewis Ship
JavaScriptSupport (and its predecessor, RenderSupport) was largely thought out
in terms of linear page rendering, not piecemeal Ajax rendering. Unlike
JavaScript which (if properly written) doesn't care about ordering, CSS is very
ordering-centric.
It is quite common for an application to include a CSS that overrides Tapestry
defaults. Further, it is likely that certain components may want to have their
own CSS to override defaults ... but an application CSS may also want to
override those CSS rules as well.
In an Ajax scenario, the component's CSS will be dynamically added to the page
... AFTER all existing CSS, including the theoretical application CSS that
should be overriding the component CSS (theoretical in this discussion, actual
in at least one of my clients).
I think a *first* approach to resolving this would be to extend Tapestry so
that a particular CSS link can be marked as the "insertion point". CSS added
via Ajax would be inserted BEFORE the insertion point (if present) rather than
at the end of the <head> element (as is done today).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
