Bug Tracker

Opened 13 years ago

Closed 13 years ago

Last modified 10 years ago

#6587 closed bug (patchwelcome)

append function causes mixed content warning on IE when on https page and content to append contains relative link

Reported by: wesleysmith Owned by:
Priority: undecided Milestone:
Component: manipulation Version: 1.4.2
Keywords: Cc:
Blocked by: Blocking:

Description

If the append function is called from a page loaded via https on IE (I tested IE7), and the text to append contains a relative link, then IE will show a mixed content warning (Page Contains Both Secure and Nonsecure Items)

I traced this for a while and it seems to be triggered when the content is appended into the document fragment near the end of jquery's clean function.

I'm sure that this is a IE bug, but perhaps there is a workaround?

This issue is seen with jquery 1.4.2, but not seen with jquery version 1.3.2

Attachments (1)

bug.htm (345 bytes) - added by wesleysmith 13 years ago.
Test case

Download all attachments as: .zip

Change History (7)

Changed 13 years ago by wesleysmith

Attachment: bug.htm added

Test case

comment:1 Changed 13 years ago by ed.eustace

Hi, I had this happen when trying to render a <object><embed></embed></object> for a swf document.

The workaround we used was to add raw html to the element:

var objectHtml = '<object><embed src="mySwf.swf"></embed></object>'; 
div.innerHtml( objectHtml );

comment:2 Changed 13 years ago by dmethvin

Component: unfiledmanipulation

comment:3 Changed 13 years ago by snover

Milestone: 1.4.3

Resetting milestone to future.

comment:4 Changed 13 years ago by snover

Priority: undecided
Resolution: patchwelcome
Status: newclosed

This is a corner case we are not going to look at since a workaround is available and it is unlikely to be discovered by many people. If you want to write a patch that fixes the issue, we would be happy to consider it.

comment:5 Changed 12 years ago by danny.j.cohn@…

This is not a good workaround. If jQuery isn't used to update the page, it is unaware of the elements that were removed and jQuery.cache does not get cleaned up.

comment:6 Changed 10 years ago by dmethvin

#13947 is a duplicate of this ticket.

Note: See TracTickets for help on using tickets.