My favorites | Sign in
Project Logo
                
Details: Show all Hide all

Last 30 days

  • Nov 09, 2009
    issue 7 (Hash parsing error) commented on by Touvan   -   There do seem to be other inconsistencies between IE and the the others (mostly, which chars will be encoded/decoded by default), and that should at least be written down somewhere. The differences can cause hard to debug endless loops (because you check what you sent to the history against what it returns, which may not be the same). Some guide around this would help. A class or filter function util to normalize the data would be very useful.
    There do seem to be other inconsistencies between IE and the the others (mostly, which chars will be encoded/decoded by default), and that should at least be written down somewhere. The differences can cause hard to debug endless loops (because you check what you sent to the history against what it returns, which may not be the same). Some guide around this would help. A class or filter function util to normalize the data would be very useful.
  • Nov 09, 2009
    issue 7 (Hash parsing error) commented on by Touvan   -   In looking into this, it looks like this is a bug in the way IE handles that kind of URL (any url with a "?" after a hash "#?"). I think it would be more appropriate to handle this in the event listener for your specific application, in the case you really need to have a query string in the hash part of the url. I'd rather not get into filtering the data that comes out of a hashChange event (don't want the extra complexity there). But I'd love to hear other thoughts on the subject.
    In looking into this, it looks like this is a bug in the way IE handles that kind of URL (any url with a "?" after a hash "#?"). I think it would be more appropriate to handle this in the event listener for your specific application, in the case you really need to have a query string in the hash part of the url. I'd rather not get into filtering the data that comes out of a hashChange event (don't want the extra complexity there). But I'd love to hear other thoughts on the subject.
  • Nov 09, 2009
    issue 8 (Fix flow problem with ExternalInterface and some versions of...) commented on by Touvan   -   Actually, I'll need to reproduce this before attempting to write code to fix it. I have been unable to cause the problem myself.
    Actually, I'll need to reproduce this before attempting to write code to fix it. I have been unable to cause the problem myself.
  • Oct 28, 2009
    issue 8 (Fix flow problem with ExternalInterface and some versions of...) reported by Touvan   -   I learned on the FlashCodersNY list that there may be an issue with calling ExternalInterface.call too close together on some versions of IE (*grumbles*). The comments suggest that there should be a 500 millisecond delay between calls. I'll combine the close calls, and try to put a limiter on the methods that need to communicate with JS Always spending my time, and my money, fixing Microsoft's mistakes.
    I learned on the FlashCodersNY list that there may be an issue with calling ExternalInterface.call too close together on some versions of IE (*grumbles*). The comments suggest that there should be a 500 millisecond delay between calls. I'll combine the close calls, and try to put a limiter on the methods that need to communicate with JS Always spending my time, and my money, fixing Microsoft's mistakes.

Earlier this year

  • Oct 20, 2009
    r36 ( ) committed by Touvan   -  
  • Oct 08, 2009
    r35 (Fixed a bug in AS3 HistoryKeeper that caused IE to behave er...) committed by Touvan   -   Fixed a bug in AS3 HistoryKeeper that caused IE to behave erratically. - Removed dependency on JSCommunicator from AS3 History Keeper, and setBrowserTitle, since a recent test revealed no actual benefit to using it. JSCommunicator was a practice in extreme premature optimization, but it contained an interesting problem, which is now solved. ;-) : - Moved AS3Communicator.js functionality to within JSCommunicator.as - it now sets itself up, and has no dependency on any external JavaScript! (There may be use for this if there are many rapid calls out to Javascript - I haven't tested that theory though - this could be completely useless! ;-P ) - Deleted AS3Communicator.js
    Fixed a bug in AS3 HistoryKeeper that caused IE to behave erratically. - Removed dependency on JSCommunicator from AS3 History Keeper, and setBrowserTitle, since a recent test revealed no actual benefit to using it. JSCommunicator was a practice in extreme premature optimization, but it contained an interesting problem, which is now solved. ;-) : - Moved AS3Communicator.js functionality to within JSCommunicator.as - it now sets itself up, and has no dependency on any external JavaScript! (There may be use for this if there are many rapid calls out to Javascript - I haven't tested that theory though - this could be completely useless! ;-P ) - Deleted AS3Communicator.js
  • Sep 07, 2009
    r34 (- tagging Beta 4) committed by Touvan   -   - tagging Beta 4
    - tagging Beta 4
  • Jul 09, 2009
    unFocus-History-2b4.zip (unFocus History Keeper 2.0 Beta 4) file uploaded by Touvan   -  
    Labels: Featured OpSys-All Type-Source
    Labels: Featured OpSys-All Type-Source
  • Jul 09, 2009
    r33 (- removed ObjectPatentMagic - added Packed library files for...) committed by Touvan   -   - removed ObjectPatentMagic - added Packed library files for RC 1
    - removed ObjectPatentMagic - added Packed library files for RC 1
  • Jun 29, 2009
    issue 7 (Hash parsing error) reported by Touvan   -   A bug report from the comments on the HistoryKeeper main page: From commenter Egor: I’m change your method “_getHash” in “unFocus-History-p.js”. See changes. My variant is more correctly: var _getHash = function() { if (/MSIE/.test(navigator.userAgent) || window.opera) { var result = /\?([^\?\#]*)$/.exec( location.href ); var search = (result && result[0]) ? result[0] : ”; return location.hash.substring(1) + search; } return location.hash.substring(1); }; Additionally: Hi. Yes. You will see bag if: http://www.yoursite.com/something?a=1&b=2#/something-anohter/?a=3&b=4 In IE & Opera a = 1 and b = 2. Params get from first “?” symbol. My variant fix this problem . Task: Investigate, and confirm.
    A bug report from the comments on the HistoryKeeper main page: From commenter Egor: I’m change your method “_getHash” in “unFocus-History-p.js”. See changes. My variant is more correctly: var _getHash = function() { if (/MSIE/.test(navigator.userAgent) || window.opera) { var result = /\?([^\?\#]*)$/.exec( location.href ); var search = (result && result[0]) ? result[0] : ”; return location.hash.substring(1) + search; } return location.hash.substring(1); }; Additionally: Hi. Yes. You will see bag if: http://www.yoursite.com/something?a=1&b=2#/something-anohter/?a=3&b=4 In IE & Opera a = 1 and b = 2. Params get from first “?” symbol. My variant fix this problem . Task: Investigate, and confirm.
  • Jun 13, 2009
    r32 (- Changed license to MIT - Added svn:keywords to most files.) committed by Touvan   -   - Changed license to MIT - Added svn:keywords to most files.
    - Changed license to MIT - Added svn:keywords to most files.
  • May 29, 2009
    r31 (- Updated tests for EventManager, FlashPlayerInfo, HistoryKe...) committed by Touvan   -   - Updated tests for EventManager, FlashPlayerInfo, HistoryKeeper, SwfHTML and SwfShim.
    - Updated tests for EventManager, FlashPlayerInfo, HistoryKeeper, SwfHTML and SwfShim.
  • May 29, 2009
    r30 (- removed WebTV code, since the entire FlashPlayerInfo scrip...) committed by Touvan   -   - removed WebTV code, since the entire FlashPlayerInfo script doesn't work in WebTV anyway.
    - removed WebTV code, since the entire FlashPlayerInfo script doesn't work in WebTV anyway.
  • May 28, 2009
    issue 5 (Update FlashPlayerInfo to utilize new versioning info) Status changed by Touvan   -   fixed in SVN r29
    Status: Fixed
    fixed in SVN r29
    Status: Fixed
  • May 28, 2009
    r29 (- Fixed Issue 5. Added methods for major, minor and bugfix v...) committed by Touvan   -   - Fixed Issue 5 . Added methods for major, minor and bugfix versions, to reflect changes to the convention in Flash Player 10 - Also cleaned up issues releated to the changes in IE. - Added getUpdateVersion for the special case Flash Player 9 updates.
    - Fixed Issue 5 . Added methods for major, minor and bugfix versions, to reflect changes to the convention in Flash Player 10 - Also cleaned up issues releated to the changes in IE. - Added getUpdateVersion for the special case Flash Player 9 updates.
  • May 28, 2009
    r28 (- Quick fix for shimMode on SwfShim.) committed by Touvan   -   - Quick fix for shimMode on SwfShim.
    - Quick fix for shimMode on SwfShim.
  • May 21, 2009
    r27 (- Major rewrite. - Fixes IE support. - Adds shimMode prope...) committed by Touvan   -   - Major rewrite. - Fixes IE support. - Adds shimMode property (it's off by default).
    - Major rewrite. - Fixes IE support. - Adds shimMode property (it's off by default).
  • May 18, 2009
    r26 (- Fixed typo in call to get initial hash value (deep link), ...) committed by Touvan   -   - Fixed typo in call to get initial hash value (deep link), which broke it.
    - Fixed typo in call to get initial hash value (deep link), which broke it.
  • May 08, 2009
    r25 (- Updates to the HistoryKeeper Actionscript 3.0 files. These...) committed by Touvan   -   - Updates to the HistoryKeeper Actionscript 3.0 files. These changes are generally significant. - Added asdocs comments.
    - Updates to the HistoryKeeper Actionscript 3.0 files. These changes are generally significant. - Added asdocs comments.
  • May 04, 2009
    issue 4 (Opera Support) Status changed by Touvan   -   I checked in a fix for Opera 9+ into SVN. I'm not sure why they are not able to detect this automatically (maybe it works sometimes?), but the fix is easy enough, so it's in. You can add it manually too, just put this somewhere in your script, if you don't want to update everything: // opera if (history.navigationMode) history.navigationMode = 'compatible';
    Status: Fixed
    I checked in a fix for Opera 9+ into SVN. I'm not sure why they are not able to detect this automatically (maybe it works sometimes?), but the fix is easy enough, so it's in. You can add it manually too, just put this somewhere in your script, if you don't want to update everything: // opera if (history.navigationMode) history.navigationMode = 'compatible';
    Status: Fixed
  • May 04, 2009
    r24 (- Added support for Opera's history.navigationMode. - Made ...) committed by Touvan   -   - Added support for Opera's history.navigationMode. - Made IE8 Hack detection more robust, and IE detectin simpler.
    - Added support for Opera's history.navigationMode. - Made IE8 Hack detection more robust, and IE detectin simpler.
  • Apr 29, 2009
    r23 (- Initial commit of Actionscript HistoryKeeper and AS3->JS c...) committed by Touvan   -   - Initial commit of Actionscript HistoryKeeper and AS3->JS communication framework (really just an easier replacement for fscommand). All of this is pretty rough - vomit draft material.
    - Initial commit of Actionscript HistoryKeeper and AS3->JS communication framework (really just an easier replacement for fscommand). All of this is pretty rough - vomit draft material.
  • Apr 20, 2009
    r22 ([No log message]) committed by Touvan   -   [No log message]
    [No log message]
  • Apr 15, 2009
    r21 (- Quick and dirty temp IE8 support (makes IE8 use the timer ...) committed by Touvan   -   - Quick and dirty temp IE8 support (makes IE8 use the timer method). - Some smaller code comment and formatting cleanups.
    - Quick and dirty temp IE8 support (makes IE8 use the timer method). - Some smaller code comment and formatting cleanups.
  • Apr 15, 2009
    issue 6 (History.js - _createAnchor creates flash in Mac Browsers) Status changed by Touvan   -   Removed in r20 http://code.google.com/p/unfocus-history-keeper/source/detail?spec=svn20&r=20
    Status: Fixed
  • Apr 15, 2009
    r20 (- removed problematic _createAnchor functionality. (Issue 6)...) committed by Touvan   -   - removed problematic _createAnchor functionality. ( Issue 6 ) - updated IE version detect to be compatible with multi-digit versions.
    - removed problematic _createAnchor functionality. ( Issue 6 ) - updated IE version detect to be compatible with multi-digit versions.
  • Jan 13, 2009
    issue 6 (History.js - _createAnchor creates flash in Mac Browsers) reported by Touvan   -   _createAnchor causes a flash in Mac Browsers. Use history keeper with a flash movie on Mac Firefox or sometimes Safari. When createAnchor adds an anchor element to the page, that anchor is blanking the flash content, until the next time the flash player is redrawn (usually it looks like a flash of no content, sometimes it's worse than that). I think this applies only to wmode="window" or whatever the default is. I think the fix will be to simply remove that functionality. That trick used to be part of IE5 support, and then migrated to this all-browser solution, because it created a way for the browser's scroll position to be recorded between hash changes. I'm not sure if anyone is using that feature - I certainly am not. I'll probably just kill this off, and be done with it. If you need a temporary workaround, comment out the innards of that function, and you'll be good to go.
    _createAnchor causes a flash in Mac Browsers. Use history keeper with a flash movie on Mac Firefox or sometimes Safari. When createAnchor adds an anchor element to the page, that anchor is blanking the flash content, until the next time the flash player is redrawn (usually it looks like a flash of no content, sometimes it's worse than that). I think this applies only to wmode="window" or whatever the default is. I think the fix will be to simply remove that functionality. That trick used to be part of IE5 support, and then migrated to this all-browser solution, because it created a way for the browser's scroll position to be recorded between hash changes. I'm not sure if anyone is using that feature - I certainly am not. I'll probably just kill this off, and be done with it. If you need a temporary workaround, comment out the innards of that function, and you'll be good to go.
  • Jan 13, 2009
    issue 3 (Javascript Errors are used incorrectly in SwfHTML) Status changed by Touvan   -   This is fixed on trunk in SVN r19.
    Status: Fixed
    This is fixed on trunk in SVN r19.
    Status: Fixed

Older

 
Hosted by Google Code