dshistory - Project Hosting on Google Code

Earlier this year Nov 12, 2009 issue 8 (JS TypeError in Opera (line 95)) reported by RichardDavies79 - There is a JavaScript error when using Opera. The error prevents further scripts (even non-dsHistory scripts) on the page from executing. I know that dsHistory currently doesn't support Opera, but you should detect Opera and just return immediately from your function so that no error is produced. What steps will reproduce the problem? 1. View demo page in Opera: http://dshistory.googlecode.com/svn/trunk/examples/demo.html 2. Open error console (Tools->Advanced->Developer Tools then click 'Error Console' tab). 3. Note JS TypeError on line 95 of http://dshistory.googlecode.com/svn/trunk/dshistory.js What is the expected output? What do you see instead? The frameWindow variable is not defined in Opera so it's causing an error. Opera should be detected and you should just return immediately to avoid errors and allow remaining JS scripts to execute. What version of the product are you using? On what operating system? Opera 10.1 Windows XP SP3 There is a JavaScript error when using Opera. The error prevents further scripts (even non-dsHistory scripts) on the page from executing. I know that dsHistory currently doesn't support Opera, but you should detect Opera and just return immediately from your function so that no error is produced. What steps will reproduce the problem? 1. View demo page in Opera: http://dshistory.googlecode.com/svn/trunk/examples/demo.html 2. Open error console (Tools->Advanced->Developer Tools then click 'Error Console' tab). 3. Note JS TypeError on line 95 of http://dshistory.googlecode.com/svn/trunk/dshistory.js What is the expected output? What do you see instead? The frameWindow variable is not defined in Opera so it's causing an error. Opera should be detected and you should just return immediately to avoid errors and allow remaining JS scripts to execute. What version of the product are you using? On what operating system? Opera 10.1 Windows XP SP3 May 15, 2009 issue 7 (Safari 4 public beta: does not work) reported by pracucci - What steps will reproduce the problem? 1. Try dshistory demo with Safari 4 public beta What is the expected output? What do you see instead? It's supposed to work. There isn't any dash after the url. What version of the product are you using? On what operating system? Safari 4 public beta on Mac OS 10.5.7 What steps will reproduce the problem? 1. Try dshistory demo with Safari 4 public beta What is the expected output? What do you see instead? It's supposed to work. There isn't any dash after the url. What version of the product are you using? On what operating system? Safari 4 public beta on Mac OS 10.5.7 Mar 31, 2009 issue 6 (Problems with back-BUTTON on IE8 (winxp pro sp3)) reported by geki007 - What steps will reproduce the problem? 1. go to demo page with ie8 2. click "Set Name-Value" and "Bind Query Vars" 3. click "Set Name-Value" and "Bind Query Vars" 4. click "Set Name-Value" and "Bind Query Vars" 5. click the back button What is the expected output? What do you see instead? on the first click its ok, the second not the third could be ok but i think it does what the second should do! What steps will reproduce the problem? 1. go to demo page with ie8 2. click "Set Name-Value" and "Bind Query Vars" 3. click "Set Name-Value" and "Bind Query Vars" 4. click "Set Name-Value" and "Bind Query Vars" 5. click the back button What is the expected output? What do you see instead? on the first click its ok, the second not the third could be ok but i think it does what the second should do! Mar 31, 2009 issue 5 (FF 3.1b3 nightly, hash value false) commented on by geki007 - It wos a firefox bug and now it's fixed! It wos a firefox bug and now it's fixed! Feb 25, 2009 issue 5 (FF 3.1b3 nightly, hash value false) commented on by geki007 - Because i think it's a FF bug, i have filled a FF bug Link: https://bugzilla.mozilla.org/show_bug.cgi?id=480263 Because i think it's a FF bug, i have filled a FF bug Link: https://bugzilla.mozilla.org/show_bug.cgi?id=480263 Feb 25, 2009 issue 5 (FF 3.1b3 nightly, hash value false) commented on by mrbarfuss - Because i think it's a FF bug, i have filled a FF bug Link: https://bugzilla.mozilla.org/show_bug.cgi?id=480263 Because i think it's a FF bug, i have filled a FF bug Link: https://bugzilla.mozilla.org/show_bug.cgi?id=480263 Feb 20, 2009 issue 5 (FF 3.1b3 nightly, hash value false) reported by geki007 - What steps will reproduce the problem? 1. go to your demo page 2. Set Name-Value, Bind Query Vars 3. Set Name-Value, Bind Query Vars 4. Remove Name-Value, Bind Query Vars What is the expected output? What do you see instead? The hash is not korrekt on FF 3.1b3 nightly, also it is false on the latest nightly of FF on FF 3.1b2 it works, bug in FF? What version of the product are you using? On what operating system? FF 3.1b3 nightly, winxp sp3 What steps will reproduce the problem? 1. go to your demo page 2. Set Name-Value, Bind Query Vars 3. Set Name-Value, Bind Query Vars 4. Remove Name-Value, Bind Query Vars What is the expected output? What do you see instead? The hash is not korrekt on FF 3.1b3 nightly, also it is false on the latest nightly of FF on FF 3.1b2 it works, bug in FF? What version of the product are you using? On what operating system? FF 3.1b3 nightly, winxp sp3 Feb 18, 2009 issue 4 (dsHistory.removeQueryVar not working also getQueryVar functi...) reported by swaroopjoe - What steps will reproduce the problem? 1. Run the demo 2. click on 'Set Name-Value'. This is working as expected 3. click on 'Remove Name-Value'. This is not working as expected If you browse through the code you will see that there is no function named getQueryVar[key]. This function is expected to get the values from the query string. Thank you. What steps will reproduce the problem? 1. Run the demo 2. click on 'Set Name-Value'. This is working as expected 3. click on 'Remove Name-Value'. This is not working as expected If you browse through the code you will see that there is no function named getQueryVar[key]. This function is expected to get the values from the query string. Thank you. Feb 13, 2009 issue 3 (history.lenght not increased in Mozilla after calling addFun...) commented on by sara.m.ribeiro - Hi Andrew, thank you for the feedback. Actually I was just using history.length for monitoring purposes... Looking at the browser history itself it would be similar. DShistory seems to work pretty ok if each page that you browse is added to the browser history (and hence history.length is incremented). And this is what is not happening in my case, in Mozilla, I suppose because of the innerHMTL thing... I'll keep investigating this then. I hope that if I find a way to force the different pages (although with same url) to be added to the broswer history, then dsHistory will do the rest :) Thanks again and best regards, Sara Hi Andrew, thank you for the feedback. Actually I was just using history.length for monitoring purposes... Looking at the browser history itself it would be similar. DShistory seems to work pretty ok if each page that you browse is added to the browser history (and hence history.length is incremented). And this is what is not happening in my case, in Mozilla, I suppose because of the innerHMTL thing... I'll keep investigating this then. I hope that if I find a way to force the different pages (although with same url) to be added to the broswer history, then dsHistory will do the rest :) Thanks again and best regards, Sara Feb 12, 2009 API (A summary of the public properties and methods of dsHistory) Wiki page edited by amattie Feb 12, 2009 issue 1 (Does not work in firefox 2) Status changed by amattie - Status: Invalid Status: Invalid Feb 12, 2009 issue 3 (history.lenght not increased in Mozilla after calling addFun...) Status changed by amattie - Sara, You made an interesting observation that I failed to point out in the docs. While the addFunction and bindQueryVars methods allow you to simulate adding to the browser history stack, it doesn't necessarily follow that all of the behind-the-scenes stuff will work as you expect. From what I recall, in the case of window.history.length, it doesn't change in Firefox when using addFunction (as you observed). I don't remember specifically whether window.history.length changes when using bindQueryVars. In designing dsHistory, one of the compromises I choose to make was to more-or-less abandon all data within the history once the user has moved on to another page. The reason for this is because dsHistory, unlike other browser history managers, allows you to add to the history using addFunction without messing with the location hash value. If you wanted to reintroduce that functionality though, you could choose to only use bindQueryVars (i.e. not using addFunction at all) and then monitoring the appropriate properties in dsHistory.QueryVars using an interval. Anyway, going back to my original point, you can't really ever rely on window.history.length to behave the way you want it to across all of the browser platforms. The best you can reasonably expect out of the different browser history managers in today's world is that the author will have normalized the API to the point where you don't have to worry about the intricacies that each browser brings to the table. Sorry to disappoint. Status: WontFix Sara, You made an interesting observation that I failed to point out in the docs. While the addFunction and bindQueryVars methods allow you to simulate adding to the browser history stack, it doesn't necessarily follow that all of the behind-the-scenes stuff will work as you expect. From what I recall, in the case of window.history.length, it doesn't change in Firefox when using addFunction (as you observed). I don't remember specifically whether window.history.length changes when using bindQueryVars. In designing dsHistory, one of the compromises I choose to make was to more-or-less abandon all data within the history once the user has moved on to another page. The reason for this is because dsHistory, unlike other browser history managers, allows you to add to the history using addFunction without messing with the location hash value. If you wanted to reintroduce that functionality though, you could choose to only use bindQueryVars (i.e. not using addFunction at all) and then monitoring the appropriate properties in dsHistory.QueryVars using an interval. Anyway, going back to my original point, you can't really ever rely on window.history.length to behave the way you want it to across all of the browser platforms. The best you can reasonably expect out of the different browser history managers in today's world is that the author will have normalized the API to the point where you don't have to worry about the intricacies that each browser brings to the table. Sorry to disappoint. Status: WontFix Feb 12, 2009 issue 3 (history.lenght not increased in Mozilla after calling addFun...) reported by sara.m.ribeiro - Hello Andrew, i'm having an issue with dshistory and Mozilla, which I hope you can help me clarify/solve. In IE, each time addFunction() is called, the history.length is increased by 1. But in mozilla this is not happening. When going to another page of my site, the addFunction is called but the history.lenght remains the same. So then, when going back, I don't really go to were it was supposed :/ Take as example this simple scenario (browser history cleaned before start): Page \| history.length \| IE Mozilla ---------------------------------------- 1. go to home page \| 1 1 2. go to contact page \| 2 1 3. go to links page \| 3 1 At this point, in Mozilla I cannot go back, because there is no history back! while in IE I can go back first to contact page and then to home page. contact and link pages are being loaded via Ajax, i.e: 1. when link is clicked a function onNavigation is called 2. on this function , we add this same function for the uri (contact or link) to dsHistory 3. then an html request is created and sent to the server (java application) which returns the html of the result page 4. finally the innerHTML of the target page (which is '_self') is replaced with the obtained html from the server. Is there anything here that could be causing the behaviour I described for history.lenght? Any idea on how to get around it? Thanks in advance and best regards, Sara Ribeiro PS.: version intially used was dsHistory, v1-beta1 $Rev: 51 $, but I getting same beahviour with the current last version dsHistory, dsHistory, v1-beta5 $Rev: 78 $ Hello Andrew, i'm having an issue with dshistory and Mozilla, which I hope you can help me clarify/solve. In IE, each time addFunction() is called, the history.length is increased by 1. But in mozilla this is not happening. When going to another page of my site, the addFunction is called but the history.lenght remains the same. So then, when going back, I don't really go to were it was supposed :/ Take as example this simple scenario (browser history cleaned before start): Page \| history.length \| IE Mozilla ---------------------------------------- 1. go to home page \| 1 1 2. go to contact page \| 2 1 3. go to links page \| 3 1 At this point, in Mozilla I cannot go back, because there is no history back! while in IE I can go back first to contact page and then to home page. contact and link pages are being loaded via Ajax, i.e: 1. when link is clicked a function onNavigation is called 2. on this function , we add this same function for the uri (contact or link) to dsHistory 3. then an html request is created and sent to the server (java application) which returns the html of the result page 4. finally the innerHTML of the target page (which is '_self') is replaced with the obtained html from the server. Is there anything here that could be causing the behaviour I described for history.lenght? Any idea on how to get around it? Thanks in advance and best regards, Sara Ribeiro PS.: version intially used was dsHistory, v1-beta1 $Rev: 51 $, but I getting same beahviour with the current last version dsHistory, dsHistory, v1-beta5 $Rev: 78 $ Feb 04, 2009 Examples (Some examples of how you can use dsHistory in your app) Wiki page edited by amattie Older Dec 08, 2008 issue 1 (Does not work in firefox 2) commented on by amattie - Please try this again and let me know. I couldn't replicate the failure, but I may have fixed the issue you ran into in some of the bug fixes I've made since September. Also, my apologies for not seeing this / addressing this sooner. Google Code doesn't notify the owner by default when a new issue is created. I've changed it so that it will notify me from now on though. Please try this again and let me know. I couldn't replicate the failure, but I may have fixed the issue you ran into in some of the bug fixes I've made since September. Also, my apologies for not seeing this / addressing this sooner. Google Code doesn't notify the owner by default when a new issue is created. I've changed it so that it will notify me from now on though. Dec 08, 2008 Examples (Some examples of how you can use dsHistory in your app) Wiki page edited by amattie Dec 08, 2008 dshistory-v1-beta5.zip (dsHistory, v1-beta5) file uploaded by amattie - Labels: Featured Labels: Featured Dec 08, 2008 r79 ([No log message]) committed by amattie - [No log message] [No log message] Dec 08, 2008 r78 (* r73 contained a flaw in the updated IE detection code) committed by amattie - * r73 contained a flaw in the updated IE detection code * r73 contained a flaw in the updated IE detection code Dec 08, 2008 r77 ([No log message]) committed by amattie - [No log message] [No log message] Dec 08, 2008 Examples (Some examples of how you can use dsHistory in your app) Wiki page edited by amattie Dec 08, 2008 Usage (A quick how-to guide for using dsHistory) Wiki page edited by amattie Dec 08, 2008 r74 ([No log message]) committed by amattie - [No log message] [No log message] Dec 08, 2008 dshistory-v1-beta4.zip (dsHistory, v1-beta4) file uploaded by amattie - Labels: Featured Labels: Featured Dec 08, 2008 r73 ([No log message]) committed by amattie - [No log message] [No log message] Dec 08, 2008 r72 (* fixed an issue where setting a hash variable, going back, ...) committed by amattie - * fixed an issue where setting a hash variable, going back, and then setting that same hash variable to another value didn't work * fixed an issue where setting a hash variable, going back, and then setting that same hash variable to another value didn't work Nov 05, 2008 r71 ([No log message]) committed by amattie - [No log message] [No log message] Oct 24, 2008 r70 ([No log message]) committed by amattie - [No log message] [No log message] Sep 28, 2008 issue 1 (Does not work in firefox 2) reported by jontro - What steps will reproduce the problem? 1. Go to demo page in firefox 2 2. Use the demo and notice it will not work What steps will reproduce the problem? 1. Go to demo page in firefox 2 2. Use the demo and notice it will not work Jul 23, 2008 r69 (more work on tests. much more to go) committed by amattie - more work on tests. much more to go more work on tests. much more to go

issue 3 (history.lenght not increased in Mozilla after calling addFun...) reported by sara.m.ribeiro - Hello Andrew, i'm having an issue with dshistory and Mozilla, which I hope you can help me clarify/solve. In IE, each time addFunction() is called, the history.length is increased by 1. But in mozilla this is not happening. When going to another page of my site, the addFunction is called but the history.lenght remains the same. So then, when going back, I don't really go to were it was supposed :/ Take as example this simple scenario (browser history cleaned before start): Page | history.length | IE Mozilla ---------------------------------------- 1. go to home page | 1 1 2. go to contact page | 2 1 3. go to links page | 3 1 At this point, in Mozilla I cannot go back, because there is no history back! while in IE I can go back first to contact page and then to home page. contact and link pages are being loaded via Ajax, i.e: 1. when link is clicked a function onNavigation is called 2. on this function , we add this same function for the uri (contact or link) to dsHistory 3. then an html request is created and sent to the server (java application) which returns the html of the result page 4. finally the innerHTML of the target page (which is '_self') is replaced with the obtained html from the server. Is there anything here that could be causing the behaviour I described for history.lenght? Any idea on how to get around it? Thanks in advance and best regards, Sara Ribeiro PS.: version intially used was dsHistory, v1-beta1 $Rev: 51 $, but I getting same beahviour with the current last version dsHistory, dsHistory, v1-beta5 $Rev: 78 $

Hello Andrew, i'm having an issue with dshistory and Mozilla, which I hope you can help me clarify/solve. In IE, each time addFunction() is called, the history.length is increased by 1. But in mozilla this is not happening. When going to another page of my site, the addFunction is called but the history.lenght remains the same. So then, when going back, I don't really go to were it was supposed :/ Take as example this simple scenario (browser history cleaned before start): Page | history.length | IE Mozilla ---------------------------------------- 1. go to home page | 1 1 2. go to contact page | 2 1 3. go to links page | 3 1 At this point, in Mozilla I cannot go back, because there is no history back! while in IE I can go back first to contact page and then to home page. contact and link pages are being loaded via Ajax, i.e: 1. when link is clicked a function onNavigation is called 2. on this function , we add this same function for the uri (contact or link) to dsHistory 3. then an html request is created and sent to the server (java application) which returns the html of the result page 4. finally the innerHTML of the target page (which is '_self') is replaced with the obtained html from the server. Is there anything here that could be causing the behaviour I described for history.lenght? Any idea on how to get around it? Thanks in advance and best regards, Sara Ribeiro PS.: version intially used was dsHistory, v1-beta1 $Rev: 51 $, but I getting same beahviour with the current last version dsHistory, dsHistory, v1-beta5 $Rev: 78 $

Earlier this year

Older