gcfavorites / mouselessbrowsing

Automatically exported from code.google.com/p/mouselessbrowsing
0 stars 0 forks source link

ALT + back arrow (and ALT + forward arrow) - causes duplicate numbering #153

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.  Use ALT + forward arrow and then ALT + back arrow
2.  All the links MLB has marked are now marked twice.   Repeatedly doing
this adds to the number of times each link is numbered. 
3.  Alternatively, this sometimes causes only some of the links to now be
numbered.  

What is the expected output?

Not having the links numbered twice.

What do you see instead?

What version of the product are you using? On what operating system?

MLB 0.5.2.1
OS - Windows XP Professional, version 2002, S.P. 3
Browser - Firefox 3.0.11

Please provide any additional information below.

Client Configuration (automatically added by MLB)
OS: WINNT, Firefox 3.0.11, MLB 0.5.2.1
MLB Configuration:
mouselessbrowsing.executeAutomaticNew: true
mouselessbrowsing.toggleExlNumpadWithDoubleStrokeNumKey: true
mouselessbrowsing.autoExecuteDelay: 500
mouselessbrowsing.keys.blurActiveElement: 0
mouselessbrowsing.initOnDomContentLoaded: false
mouselessbrowsing.disableAllIds: false
mouselessbrowsing.keys.toggleMLB: 1760
mouselessbrowsing.keys.toggleExlusiveUseOfNumpad: 304
mouselessbrowsing.keys.scrollUp: 1744
mouselessbrowsing.disableMLB: false
mouselessbrowsing.debug: false
mouselessbrowsing.styleForFrameIdSpan: position:fixed; top:0; left:0;
font-size:xx-small;line-height:130%;;
border-color:black; border-width:1px; border-style:solid;
-moz-border-radius:2px;
padding:0px 2px 0px 2px;
z-index:500;
background-color:#D6E3FE;
mouselessbrowsing.styleForIdSpan: font-family:arial, sans-serif;
font-size:xx-small; line-height:130%;
border-width:1px; border-style:solid;-moz-border-radius:2px;
padding:0px 2px 0px 2px;
vertical-align:center;
margin-left:2px; 
max-width:20px; max-height:10px;
overflow:visible;float:none;
mouselessbrowsing.keys.openInCoolirisPreviewsPostfixKey: 1696
mouselessbrowsing.idType: NUMERIC
mouselessbrowsing.showKeybufferInStatusbar: true
mouselessbrowsing.keys.clearKeybuffer: 432
mouselessbrowsing.maxIdNumber: 1000
mouselessbrowsing.enableOtherIds: true
mouselessbrowsing.disableAutomaticPageUpdateOnChange: false
mouselessbrowsing.keys.scrollDown: 1712
mouselessbrowsing.siteRules: <listbox
xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"
id="siteRulesLB" prefid="mouselessbrowsing.siteRules" flex="1"
disabled="false"><listhead><listheader label="URL Pattern"/><listheader
align="center" style="display: none;"/><listheader style="display:
none;"/><listheader style="display: none;"/></listhead><listcols><listcol
flex="1"/><listcol style="display: none;"/><listcol style="display:
none;"/><listcol style="display: none;"/></listcols></listbox>
mouselessbrowsing.executeAutomatic: false
mouselessbrowsing.keys.selectLink: 260
mouselessbrowsing.showIdsOnDemand: false
mouselessbrowsing.version: 0.5.2.1
mouselessbrowsing.exclusiveNumpad: false
mouselessbrowsing.pixelsToScroll: 150
mouselessbrowsing.enableImgLinkIds: true
mouselessbrowsing.idChars: 
mouselessbrowsing.keys.blockKeyboardInputForMlb: 0
mouselessbrowsing.keys.toggleAllIds: 1762
mouselessbrowsing.keys.toggleEnableDisableMLB: 1761
mouselessbrowsing.keys.openInNewWindowPostfixKey: 1776
mouselessbrowsing.modifierForOpenInCoolirisPreviews: -1
mouselessbrowsing.keys.addSiteRule: 1319
mouselessbrowsing.keys.openConfig: 1239
mouselessbrowsing.keys.historyBack: 1776
mouselessbrowsing.smartPositioning: true
mouselessbrowsing.debug.perf: false
mouselessbrowsing.modifierForOpenInNewWindow: 3
mouselessbrowsing.modifierForOpenInNewTab: 1
mouselessbrowsing.modifierForWritableElement: 2
mouselessbrowsing.enableFrameIds: true
mouselessbrowsing.showMlbMenu: true
mouselessbrowsing.keys.historyForward: 1696
mouselessbrowsing.showTabIds: true
mouselessbrowsing.showMlbIconInStatusbar: true
mouselessbrowsing.filterDuplicateLinks: true
mouselessbrowsing.enableLinkIds: true
mouselessbrowsing.executeInstantlyWhenIdUnique: false
mouselessbrowsing.enableFormElementIds: true
mouselessbrowsing.keys.openInNewTabPostfixKey: 1712
mouselessbrowsing.keys.updatePage: 1713

Original issue reported on code.google.com by joefiesta@verizon.net on 11 Jul 2009 at 2:00

GoogleCodeExporter commented 9 years ago
Thanks for your feedback!
I run the same configuration but of course don't have this problem, so I need 
some
more information.
Does this behavior occurs on every page or only on specific ones?

Original comment by Rudolf....@gmail.com on 12 Jul 2009 at 4:03

GoogleCodeExporter commented 9 years ago
I find it happens on only one site:  HTTP://dictionary.reference.com

Original comment by joefiesta@verizon.net on 24 Jul 2009 at 1:24

GoogleCodeExporter commented 9 years ago
I should add that it doesn't actually happen on that page.   After going to
dictionary.reference.com, enter a word to be looked up in the dictionary.  
Then, from
the page to which you are taken you should find that you can re-create the 
problem.

Original comment by joefiesta@verizon.net on 24 Jul 2009 at 2:48

GoogleCodeExporter commented 9 years ago
I should also add that I use the NOSCRIPT addon (1.9.6.9) and dissallow scripts 
to
run at REFERENCE.COM.

Hmm, more info.   If I allow scripts to run at REFERENCE.COM, the problem 
disappears.
 I presume, then, that disabling the NOSCRIPT addon should make the problem disappear
as well.   

Original comment by joefiesta@verizon.net on 24 Jul 2009 at 2:58

GoogleCodeExporter commented 9 years ago
Thanks for your feedback!
But even if I run the same NOSCRIPT configuration I could not reproduce the 
error :-(
I think I will add a remark under my Known Issues section that there could be 
side
effects with noscript

Original comment by Rudolf....@gmail.com on 2 Sep 2009 at 7:52

GoogleCodeExporter commented 9 years ago
Hello.   I have just discovered that I can no longer re-create this behavior at 
dictionary.com.    They are constantly changing their web site, and I strongly 
suspect now that the problem was the result of something they were doing.  

Please close this issue.  I have other (new) issues with Dictionary.com but (1) 
I am not sure they are caused by MLB and (2) not sure they are worth reporting. 
 Should I change my mind, I will open a new ticket.   

Thank you.

Original comment by joefiesta@verizon.net on 2 Jun 2011 at 1:03

GoogleCodeExporter commented 9 years ago

Original comment by Rudolf....@gmail.com on 9 Jun 2011 at 7:51