[ews.eclipse.technology.rap] Re: Images in Table HTTPS IE

[Ivan Furnadjiev <ivan@xxxxxxxxxxxxxxxxx>]

Hi Philipp,

you can try to resolve the path with qooxdoo Alias.js in 
TableItem.js#_renderImage like this:
---
var url = qx.io.Alias.getInstance().resolve( image );
node.style.backgroundImage = "url(" + url+ ")";
---

Best,
Ivan

Stefan Roeck wrote:
> Hi Philipp,
>
> I think the reason is that the table items write their image markup 
> directly without using qx-classes (See TableItem.js _getImageMarkup) 
> in RAP 1.2.
>
> This seems to have been changed in RAP 1.3.
>
>
> Regards,
> Stefan.
>
>
> Philipp Eichhorn schrieb:
> > Hi,
> >
> > I think, I might be stuck in a HTTPS+IE trap again.
> > I'm using RAP 1.2 with the latest qooxdoo patches.
> >
> > Sidenote: The latest alias.js patch resolved a lot of issues I was 
> > having.
> >
> > Now, I have a Table using JFace TableViewer and fill it with Images 
> > using a TableLabelProvider. The TableLabelProvider.getColumnImage(..) 
> > does nothing else than Graphics.getImage(..). This works fine in 
> > every Browser except the IE, where I get a "secure and non-secure 
> > content" warning. If the TableLabelProvider.getColumnImage(..) return 
> > null the warning doesn't appear.
> > Interesting is, that this issue seems to be fixed in the HEAD version 
> > of RAP 1.3.
> >
> > Again sidenode: I have an other major issue with RAP 1.3 and existing 
> > CustomWidgets, which work with RAP 1.2. So RAP 1.3 is no option for now.
> >
> > On JavaScript side the RAP 1.2 and RAP 1.3 I'm using are identical, 
> > so I rule out a JavaScript issue.
> > I was wondering if someone has an idea where to look for the 
> > differences between RAP 1.2 and 1.3 concerning this issue, this would 
> > save me a lot of time. A existing Fix would be even better.
> > I'm not sure if there will be a new RAP 1.2 version coming up, but 
> > if, I would appreciate, if some of the nice fixes made for RAP 1.3 
> > would be applied to RAP 1.2 as well.
> >
> > Kind Regards
> >
> > Philipp