-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hammerhead is not initialized in the rewrited iframe with same-domain url in IE #1325
Comments
I'm working on this |
…omain url in IE` (close DevExpress#1325)
…omain url in IE` (close DevExpress#1325)
Just a reminder: changes from #1636 should be reverted after a fix for this issue. |
Is this being worked at? |
@ericaprieto, Currently, we don't work on this issue. If you have a similar one, please submit a separate report. If you'd like to contribute your fix, please create a pull request. |
For the team. <!doctype html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport"
content="width=device-width, user-scalable=no, initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0">
<meta http-equiv="X-UA-Compatible" content="ie=edge">
<title>Document</title>
</head>
<body>
<script>
var iframe = document.createElement('iframe');
iframe.id = 'test' + Date.now();
iframe.addEventListener('load', function() {
this.contentDocument.write('<a href="http://domain.com/link">Link</a>');
});
document.body.appendChild(iframe);
</script>
</body>
</html> DevTools commands to run:
|
This issue has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this issue in the future. If it still affects you or you have any additional information regarding it, please leave a comment and we will keep it open. |
We're closing this issue after a prolonged period of inactivity. If it still affects you, please add a comment to this issue with up-to-date information. Thank you. |
related with #1312
The text was updated successfully, but these errors were encountered: