Chris Heiland wrote: > > In the XDV control panel there are two settings that should affect > when the the site is styled by XDV. The first is Domains which behaves > as expected by enabling the transformations and setting the HTTP_X_XDV > when a matching domain is found. The second is Unstyled paths which > stops the transformations but does not set the HTTP_X_XDV variable. > > We are using HTTP_X_XDV as a condition to set if files in the > portal_css and portal_javascript registries get loaded. My proposal is > to not set HTTP_X_XDV if any of the unstyled paths are matched. I > suggest because anything under Unstyled paths should behave the same > way as Domains. Not applying transformations while loading custom > js/css can create issues. > > I've created a patch to change the behavior as proposed but wanted to > ask if there is any reason why XDV behaves this way. >
Unstyled paths is meant to account for the kupu/TinyMCE blank page and any other special resources that should not be transformed, but are not in and of themselves navigable 'pages'. For kupu at least, you want the rich text iframe to have the same styling applied to it as the parent page, so in this case *not* loading the custom js/css would create issues. What are you trying to use unstyled paths for? Laurence -- View this message in context: http://plone.293351.n2.nabble.com/XDV-HTTP-X-XDV-for-Unstyled-Paths-tp6061851p6062694.html Sent from the Product Developers mailing list archive at Nabble.com. _______________________________________________ Product-Developers mailing list [email protected] https://lists.plone.org/mailman/listinfo/product-developers
