{"id":24879,"date":"2016-09-11T03:01:37","date_gmt":"2016-09-10T17:01:37","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=24879"},"modified":"2016-09-10T21:37:53","modified_gmt":"2016-09-10T11:37:53","slug":"legend-for-and-from-html-map-element-geolocation-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/legend-for-and-from-html-map-element-geolocation-tutorial\/","title":{"rendered":"Legend for and from HTML Map Element Geolocation Tutorial"},"content":{"rendered":"
\"Legend<\/a>

Legend for and from HTML Map Element Geolocation Tutorial<\/p><\/div>\n

We thought we might have finished with the thread of blog postings last ending with Legend for and from HTML Map Element CSS Tutorial<\/a> as shown below, but we hadn’t banked on the significance of the ideas of window.postMessage<\/i><\/a>, and want to explore more about this.<\/p>\n

Last time talking about this, with window.postMessage<\/i><\/a> work, we used it to have a webpage from another domain have its contents be included in a parent “cross-domain” HTML iframe element’s contents. Well, that’s good and all, but is limiting the scope of what window.postMessage<\/i><\/a> could be used for, don’t you think?<\/p>\n

So, today, it may seem a tad academic, but nonetheless throwing up some ideas for you to peruse, we hope, we use Javascript geolocation functions to show you the location of “parent” webpage and “child” HTML iframe webpage, and, of course, it being Javascript “client” geolocation being asked, we should get a close match, like right on top of each other … we got it on our Google Map Chart output to be here in a middle room of the house and the child being over by that same room’s window, making this laptop approximately 1.16 metres wide … we wish?! But you know what we mean here, we hope. It is more about your imagination to do with what you want to do here, as to how you apply these thoughts yourself. We might involve serverside (ie. web server) information in blog postings to come, but, just for now see legend_via_map.htm<\/a> (still helped out by “sometimes called” PHP child iframe coding logic in legend_via_map.php<\/a>) changed in this way<\/a> as far as the parent goes. We also adjusted one child called livingroom.htm<\/a> to understand what to do to accomodate the parent … “off Facebook now, Dad” … in this way<\/a> via a call from the parent to the child like ESL Vocabulary – Living Room<\/a> (with geolocation).<\/li>\n

Here is a geolocation live run<\/a> link versus a no geolocation live run<\/a> link. Hope you try them out.<\/p>\n

\n

Previous relevant Legend for and from HTML Map Element CSS Tutorial<\/a> is shown below.<\/p>\n

\"Legend<\/a>

Legend for and from HTML Map Element CSS Tutorial<\/p><\/div>\n

Our “Legend for and from HTML Map Element” blog posting thread continues today wrapping up a few issues and fixing some bugs, discovering for the first time for us, a true use for multiple background images, so please read on for more information, from our list of today’s major changes below …<\/p>\n