Bug 30211 - Introduce publication-specific CSS path in lenya/xslt/bxeng/index-xhtml.xsl
Summary: Introduce publication-specific CSS path in lenya/xslt/bxeng/index-xhtml.xsl
Status: NEW
Alias: None
Product: Lenya
Classification: Unclassified
Component: Bitflux Integration (show other bugs)
Version: 1.2
Hardware: Other other
: P3 enhancement
Target Milestone: 2.0.1
Assignee: Lenya Developers
Depends on:
Reported: 2004-07-20 15:38 UTC by Johannes Jander
Modified: 2007-07-16 02:20 UTC (History)
1 user (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Jander 2004-07-20 15:38:07 UTC
The publication-specific usecase-bxeng.xmap creates a pipeline to show the BXE
by calling lenya/xslt/bxeng/index-xhtml.xsl which (among others) defines the
<head> section. 

Inside the <head> section, a css-link is generated by  <xsl:attribute
select="$context"/>/bxeng/css/editor.css</xsl:attribute>  which points to a
global editor.css. 

usecase-bxeng.xmap provides a variable $publicationid which is not used in
xhtml-index.xsl. By evaluating this variable, index-xhtml.xsl could point the
CSS-link to a publication specific style sheet, like:  <xsl:attribute
name="href"><xsl:value-of select="$context"/>/<xsl:value-of
select="$publicationid"/>/bxeng/css/editor.css</xsl:attribute> or link to a
global and a publication-specific CSS.

Publications that make use of CSS2 to define placement and design of their pages
are likely to conflict with the editor.css by z-indexing and/or positioning. A
publications-specific editor.css would be a natural way to solve those conflics.
Comment 1 Gregor J. Rothfuss 2004-10-29 03:28:10 UTC
this should be solved with the fallback:// protocol.

johannes, feel like sending a patch?