Re: [orion-dev] Editor changes - removing the IFRAME

["Mihai Sucan" <msucan@xxxxxxxxxxx>]

Hello Silenio and John!

Just a quick note that the problems John has with the updated Orion  
integration do "ring a bell" for me. This is what I would be most  
concerned about when removing the iframe: styles from the parent page can  
now affect Orion quite badly. I had this problem when I did my old  
PaintWeb project. If I were to redo PaintWeb, I'd put it in iframe now.

For now, there's no way to isolate the styling of Orion from the styling  
of the page. This makes Orion editor integration harder, in complex web  
apps.

Obviously, having everything in an iframe brings a different set of  
problems. These need to be weighed against benefits.


(Luckily this particular problem will not affect Mozilla's integration: we  
already wrap Orion into its own iframe.)


Best regards,
Mihai



Le Wed, 21 Mar 2012 20:16:58 +0200, Silenio Quarti  
<Silenio_Quarti@xxxxxxxxxx> a écrit:

> You might have problems with drag selection on Chrome. If the editor is
> inside of an IFRAME, it will not receive mouse move events (while
> dragging) when the mouse is outside of the editor (IFRAME). The editor  
> had
> a work around that would hook mouse move listeners in the outer document.
> This work around was removed.
>
> You may also have to convert coordinates returned by the editor since
> these coordinates will be relative to the IFRAME. This might not be an
> issue if you do not talk to the editor from the outer document.
>
> What kind of styles are affecting the editor? I am curious to see if it  
> is
> something the editor should try to fix. For example, I know that setting
> lineHeight on a parent of the editor affected it badly, so I had to
> overwrite it.
>
> Silenio