• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

It just hit me

Originally posted by: notfred
Uh, do you have an actual resonable explantion for that, or can I call you an idiot now?

Google maps works by making an asynchronous call to the google servers to grab the adjacent map segments, and instead of reloading the whole page, just refreshes the div that the map is in. Div's pretty much are frames for xml.
 
Originally posted by: AccruedExpenditure
Originally posted by: notfred
Uh, do you have an actual resonable explantion for that, or can I call you an idiot now?

Google maps works by making an asynchronous call to the google servers to grab the adjacent map segments, and instead of reloading the whole page, just refreshes the div that the map is in. Div's pretty much are frames for xml.

Frames contain separate documents, DIVs don't. You can use Ajax to change the contents of a div, a span, a table, a link, or anything else, not just a div. And even if it was just a div, that might mean DIVS = FRAMES, but it still doesn't mean AJAX = FRAMES.
 
Originally posted by: notfred
Originally posted by: AccruedExpenditure
Originally posted by: notfred
Uh, do you have an actual resonable explantion for that, or can I call you an idiot now?

Google maps works by making an asynchronous call to the google servers to grab the adjacent map segments, and instead of reloading the whole page, just refreshes the div that the map is in. Div's pretty much are frames for xml.

Frames contain separate documents, DIVs don't. You can use Ajax to change the contents of a div, a span, a table, a link, or anything else, not just a div. And even if it was just a div, that might mean DIVS = FRAMES, but it still doesn't mean AJAX = FRAMES.

I agree, but I provided you with adequate actual resonable explantion you're forbidden from calling me an idiot.
 
Originally posted by: AccruedExpenditure
Originally posted by: notfred
Uh, do you have an actual resonable explantion for that, or can I call you an idiot now?

Google maps works by making an asynchronous call to the google servers to grab the adjacent map segments, and instead of reloading the whole page, just refreshes the div that the map is in. Div's pretty much are frames for xml.

That sentence reeks of a man who rarely gets laid.

 
Originally posted by: Rudee
Originally posted by: AccruedExpenditure
Originally posted by: notfred
Uh, do you have an actual resonable explantion for that, or can I call you an idiot now?

Google maps works by making an asynchronous call to the google servers to grab the adjacent map segments, and instead of reloading the whole page, just refreshes the div that the map is in. Div's pretty much are frames for xml.

That sentence reeks of a man who rarely gets laid.

I'm actually closing in on a two week drought with no end in site. Search previous threads for reasons.
 
They're similar in that both AJAX (along with pages generated using data from the POST method) and frames make it kind of difficult for a user to bookmark the page that they're seeing without some fancier functionality ala Google Maps. AJAX and a lot of dynamic pages also render the back and forward buttons in your browser useless, while frames still allow for that functionality.
 
Back
Top