Opened 15 years ago

Closed 15 years ago

#2302 closed defect (fixed)

BackgroundIFrame iframe src fixes for ie not applied to ie7

Reported by: jkuhnert Owned by: jkuhnert
Priority: high Milestone: 0.9
Component: Accessibility Version: 0.4.1
Keywords: Cc:
Blocked By: Blocking:


It looks like ie7 has the same iframe security warnings when working with ssl requests that earlier versions of ie have.

Change History (6)

comment:1 Changed 15 years ago by jkuhnert

Resolution: fixed
Status: newclosed

(In [7025]) Changed ie check to check the existance of the more generic value instead of looking for a specific version. As it is unlikely that dojo supports anything prior to ie 5.0 it doesn't really seem worth the effort or extra code to do such a verbose check anyways. Fixes #2302.

comment:2 Changed 15 years ago by jkuhnert

Resolution: fixed
Status: closedreopened

Last fixed incorrectly used (apparently only works in specific cases? )

comment:3 Changed 15 years ago by Adam Peller

Is this still a bug?

comment:4 Changed 15 years ago by jkuhnert

I'm not sure if it's in 0.9 but it definitely was in 0.4.3 still.

One of the Tapestry users tracked it down though, something in dojo.a11y I guess?

" See this Blog entry I found:

All that is needed in the above function is this line before the removeChild() call at the end: = "";

I overrode this method in my local code and it got rid of the mixed content warning. Looks like a bug report needs to be filed with Dojo (I don't have access to that).

This code is called whenever a widget is built, from widget.js, which is also why I noticed so many requests for tab_close.gif in my server log."

comment:5 Changed 15 years ago by Adam Peller

please apply/test on the 0.4.x branch or close, unless this problem persists in 0.9. Thanks

comment:6 Changed 15 years ago by bill

Component: HTMLAccessibility
Resolution: fixed
Status: reopenedclosed

Ah, I see, not BackgroundIframe? (which doesn't do anything on IE7) but dojo.a11y... that does load an image just to see if images are displayed on the screen, or something like that. But not done in 0.9, so therefore this is fixed in 0.9.

Note: See TracTickets for help on using tickets.