[Tickets #10092] Re: Portal button does nothing in Dimp iframe mode

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/10092
------------------------------------------------------------------------------
  Ticket             | 10092
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Portal button does nothing in Dimp iframe mode
  Queue              | IMP
  Version            | 5.0.3
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2011-05-18 16:52) wrote:

>> However this part you are not going to like - the Portal doesn't work
>> correctly with iframes on.  And I'm not sure we can realistically
>> make it work either without adding a bunch of hackish code.  The
>> problem is that any link within the iframe that eventually opens up
>> IMP again (e.g. the newmail folder summary) will cause IMP to be
>> fully reloaded within the IFRAME.  So you end up with 2 sidebars.
>
> Didn't you move the old dynamic portal to Horde at one point?

Yes.  And that is precisely the problem.  We used to have old hackish  
code embedded in the portal view code that would attempt to workaround  
the living in an IFRAME issue.  Not only was the code not 100%  
reliable, but it was also necessarily removed when the portal code  
moved to horde because it was completely dimp specific.

>> Which begs the question - why don't we just get rid of iframe
>> entirely?  It doesn't work properly, and won't ever work properly,
>> unless the proper framework is implemented in Horde (*NOT* IMP).
>> Until that happens, it is going to be prohibitively difficult to try
>> to support.
>
> We need it for preferences for example, and it was a requirement of  
> SAPO (and makes sense for everyone using IMP, or Kronolith for that  
> matter, as the main application) to stay in the ajax view when  
> displaying other non-ajax Horde apps.

I understand the reasons.  The problem is that it is completely  
hackishly put together.  We had an opportunity to standardize this for  
Horde 4, but nobody was interested.  Therefore, my belief is that it  
isn't appropriate to keep around if it isn't working correctly.