Which version of this file are you patching? That change has already been made to mozilla-central's copy, as far as I can tell: http://mxr.mozilla.org/mozilla-central/source/toolkit/content/customizeToolbar.js#784
Comment on attachment 392490 [details] [diff] [review] A patch to declare the dragAfter variable. Ah, that makes sense. I'm using the copy from http://mxr.mozilla.org/mozilla1.9.1/source/toolkit/content/customizeToolbar.js#784 (I did do a search for the error message in bugzilla, but nothing showed up.) Thanks!
We can take just that fix on the branch if you'd like.
Component: Toolbars → Toolbars and Toolbar Customization
Product: Firefox → Toolkit
QA Contact: toolbars → toolbars
Version: Trunk → 1.9.1 Branch
I wouldn't bother, since it doesn't really hurt anything, it's just another debug message for me to ignore. :)
I think it's worth taking, just because of the noise involved in "is there anything in the error console?" "yeah, it says 'assignment to undeclared variable dragAfter'" "no, that's known and unrelated, is there anything else?"
Phil's been here longer than I have, so I'll go with his opinion. Can we take that fix on the branch please? Thank you, Blake.
Created attachment 394903 [details] [diff] [review] Just like the trunk, for 1.9.1 Well, then let's do it exactly like the trunk does (we can't take the patch that fixed it on the trunk, since that was the giant "Switch to using the new drag-drop API" patch). Drivers: it's not just a silly "fix a warning," since having it undeclared means that if an extension stupidly uses a global named dragAfter, their value will get clobbered, but only in the miserable-to-reproduce case after a user customizes toolbars *and* drags something. There's a microscopic but non-zero chance that someone shipped an extension which is actually intending to use the accidental global dragAfter with its value after customizing (at which point it would be set to something of no use at all to anyone outside that function, so I can't picture why anyone would), but that's extremely unlikely, especially compared to the chances of someone using their own dragAfter global. (And neither use shows up in mxr-test's index of AMO addons, though I wouldn't count on that being up to date.)
Assignee: nobody → philringnalda
Status: NEW → ASSIGNED
Attachment #394903 - Flags: review?(gavin.sharp)
Attachment #394903 - Flags: review?(gavin.sharp) → review+
Attachment #394903 - Flags: approval184.108.40.206?
Attachment #394903 - Flags: approval220.127.116.11? → approval18.104.22.168?
Comment on attachment 394903 [details] [diff] [review] Just like the trunk, for 1.9.1 Approved for 22.214.171.124, a=dveditz for release-drivers
Attachment #394903 - Flags: approval126.96.36.199? → approval188.8.131.52+
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
status1.9.1: --- → .4-fixed
Resolution: --- → FIXED
Whiteboard: [needs approval]
Verified with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:184.108.40.206pre) Gecko/20090908 Shredder/3.0b4pre ID:20090908033759
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.