[Tickets #11407] Re: All header link tags in all applications

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/11407
------------------------------------------------------------------------------
  Ticket             | 11407
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | All header link tags in all applications
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
-State              | Assigned
+State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2012-09-05 15:13) wrote:

I don't see this.

For example, going to the portal page (where I am displaying an imp,  
turba, nag, and ingo block), I see these link tags:

<link href="/horde/imp/themes/default/block/screen.css"  
rel="stylesheet" type="text/css" />
<link href="/horde/ingo/themes/default/block/screen.css"  
rel="stylesheet" type="text/css" />
<link href="/horde/turba/themes/default/block/screen.css"  
rel="stylesheet" type="text/css" />
<link href="/horde/nag/themes/default/screen.css" rel="stylesheet"  
type="text/css" />
<link href="/horde/themes/default/screen.css" rel="stylesheet"  
type="text/css" />
<link href="/horde/themes/default/mozilla.css" rel="stylesheet"  
type="text/css" />
<link href="/horde/themes/default/graphics/favicon.ico" rel="SHORTCUT ICON" />
<link rel="alternate" type="application/atom+xml"  
href="https://bigworm.curecanti.org/horde/kronolith/feed/index.php?c=slusarz"  
/>  <title>Horde :: My Portal</title>

Those CSS definitions are all expected, as they are needed to show the  
portal blocks.  The shortcut icon displays the appropriate icon for  
the application that rendered the page (horde).

The kronolith link shouldn't be in there, but this isn't a PageOutput  
issue but rather a problem with the Kronolith app _init() method that  
I have mentioned multiple times previously (there is way too much  
initialization that goes on in there outside of basic app  
initialization; i.e. no browser output elements should ever be put in  
there).  I personally don't know enough about Kronolith's init  
mechanism to be able to move this to somewhere more appropriate (i.e.  
a standardized output method, like IMP::header(), that will queue  
browser output elements only when the application is responsible for  
outputting the page).