Skip to content

Commit dda5683

Browse files
authored
fix: resolves conflicts sync-29216730 with master
Pull Request: #239
1 parent 583e396 commit dda5683

File tree

1 file changed

+0
-4
lines changed
  • 3-frames-and-windows/03-cross-window-communication

1 file changed

+0
-4
lines changed

3-frames-and-windows/03-cross-window-communication/article.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -114,9 +114,6 @@ And now an example with the same origin. We can do anything with the embedded wi
114114

115115
### Please wait until the iframe loads
116116

117-
<<<<<<< HEAD
118-
When an iframe is created, it immediately has a document. But that document is different from the one that finally loads into it!
119-
=======
120117
By definition, two URLs with different domains have different origins.
121118

122119
But if windows share the same second-level domain, for instance `john.site.com`, `peter.site.com` and `site.com` (so that their common second-level domain is `site.com`), we can make the browser ignore that difference, so that they can be treated as coming from the "same origin" for the purposes of cross-window communication.
@@ -143,7 +140,6 @@ When an iframe comes from the same origin, and we may access its `document`, th
143140
Upon its creation an iframe immediately has a document. But that document is different from the one that loads into it!
144141

145142
So if we do something with the document immediately, that will probably be lost.
146-
>>>>>>> 29216730a877be28d0a75a459676db6e7f5c4834
147143

148144
Here, look:
149145

0 commit comments

Comments
 (0)