Last Comment Bug 125419 - [META]Add AppleScript support and capabilities to Mozilla on Mac, e.g. AppleScript/OSA Script menu
: [META]Add AppleScript support and capabilities to Mozilla on Mac, e.g. AppleS...
Status: NEW
: meta
Product: Firefox
Classification: Client Software
Component: General (show other bugs)
: Trunk
: All Mac OS X
P5 enhancement with 72 votes (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
: 308558 (view as bug list)
Depends on: 5701 5704 61356 156013 352254 5705 46407 149529 156010 158386 166199 1127514
Blocks: 158019 243543 158388 164968
  Show dependency treegraph
Reported: 2002-02-13 19:56 PST by Joel Nelson (don't send email)
Modified: 2016-06-23 11:55 PDT (History)
24 users (show)
samuel.sidler+old: wanted1.9.0.x-
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Description User image Joel Nelson (don't send email) 2002-02-13 19:56:03 PST
Add AppleScript support and capabilities to Mozilla on Mac OS 9 and X.  This
would include the Scripting Dictionary which is built-in to AppleScript
compatible Mac applications, adding a Script menu to the menu bar, and adding
"launch AppleScript" as an option in message rules.
Comment 1 User image R.K.Aa. 2002-02-13 20:09:00 PST
Dup of bug 58590?
DoJavascript event: bug 5704
Better AE support: bug 5701
Implement advanced XPConnect-to-AppleScript/OSA glue layer: bug 61356
Comment 2 User image Joel Nelson (don't send email) 2002-02-13 20:28:34 PST
It is similar to those four bugs although still a little different.  I would
recommend leaving it as a separate bug although you could mark it as duplicate
if needed.  This bug is more of a summary of the entire problem, while the other
bugs are more to individual issues with AppleScript.
Comment 3 User image Greg K. 2002-07-17 16:18:52 PDT
Let's keep to one issue per bug, please. Making this one about adding the Script menu. Joel, 
please file another about message rules only.
Comment 4 User image Joel Nelson (don't send email) 2002-07-17 17:22:44 PDT
Marking OS to "All" to include Mac OS 8, Mac OS 9 and Mac OS X.  (Was: Mac OS 9)
Comment 5 User image David Bradley 2002-07-18 12:55:04 PDT
Should a meta bug be created, or this turned into that?
Comment 6 User image Phil Schwartau 2002-07-18 13:25:59 PDT
From Comment #2, sounds like this should be the meta bug. 
Reassigning to Tracking component and adding the bugs mentioned
in Comment#1 as dependencies.

If anyone knows of any other AppleScript issues filed in Bugzilla,
please add them as dependencies, too -
Comment 7 User image Jean-Pierre Melkonian 2002-07-30 12:35:13 PDT
I add my bugs (or enhancements)
bug 156010
bug 156013
bug 158386
bug 158388
Comment 8 User image Greg K. 2002-08-28 10:23:50 PDT
OS should not be All (that includes LinuxPPC). Setting to 8.5, since that's the
oldest supported Mac OS at this point.
Comment 9 User image Jo Hermans 2003-04-12 03:11:46 PDT
Shouldn't we move this to Mac OS X ? Mac OS 8.5 and 9 support is dead now ...
Comment 10 User image Samir Gehani 2003-04-29 17:25:06 PDT
adt: removing nsbeta1 nomination; nominate bugs indiviually as appropriate.
Comment 11 User image Torben 2003-08-14 12:34:19 PDT
Updating OS to a supported one.
Comment 12 User image Dave Townsend [:mossop] 2005-09-14 14:00:33 PDT
*** Bug 308558 has been marked as a duplicate of this bug. ***
Comment 13 User image db 2008-03-30 17:09:01 PDT
Any updates on this issue?
Comment 14 User image Dave Miller [:justdave] ( 2008-04-05 19:11:40 PDT
I've seen the lack of this noted on a couple reviews of the Firefox 3 betas recently. Certainly too major to make it into Firefox 3, but probably worth getting back on the radar.  I think wanted-next would be more appropriate than wanted1.9.0.x, but it doesn't seem to want to let me pick that one.
Comment 15 User image Samuel Sidler (old account; do not CC) 2008-08-17 16:01:22 PDT
Moving flags around since wanted1.9.1 and blocking1.9.1 now exist.
Comment 16 User image cynthia.lockley 2008-10-23 12:34:27 PDT
Broken AppleScript support in Firefox 3 cripples URL Manager Pro and other bookmark manager applications for Mac OS X because they cannot get the name and URL of the current web page. This was my experience in OS X 10.4.11 and now in OS X 10.5.5. I get a message that there is no browser running or there is no browser window open.
Comment 17 User image Samuel Sidler (old account; do not CC) 2008-10-23 12:43:11 PDT
Comment 16 is bug 427448, which is fixed on the trunk.
Comment 18 User image bluloo 2009-02-18 15:36:29 PST
Lack of AppleScript support makes FF less useful for research because it doesn’t play well with desktop apps, like DevonThink, intended to compliment built in OS X technologies, such as AppleScript.
Comment 19 User image HMJ 2010-05-08 11:22:28 PDT
It looks like it has been a very long time since this problem was first raised, and nothing so far has been done about it and no feedback is evident from Mozilla. There is still no support for Applescript in FF 3.6.3 (as of 5/8/2010) for Mac OSX (now at 10.6.3), and that means I still cannot use URL Manager Pro to manage cross browser bookmarks.  Why has nothing been done about this?
Comment 20 User image Aaron 2010-05-10 14:14:45 PDT
This addition is important in so many ways to mac users... it makes me think that there must not be any mac users on the development team, otherwise this would have been done a long time ago. I should learn how to write for mozilla, but I think it may be a while before I understand it enough to fix this issue.
Comment 21 User image Craig Williams 2010-05-11 10:12:43 PDT
Yes, please add AppleScript support. Thanks!
Comment 22 User image HMJ 2010-05-11 12:48:00 PDT
Would someone at Mozilla please respond to these requests, or explain why this will/cannot be done?
Comment 23 User image Josh Aas 2010-05-11 14:16:42 PDT
We are aware that people want better AppleScript support but simply put, it has not been a high enough priority to get developer time. We would, of course, always accept a patch contribution.

We don't need any more "me too" comments here, thanks.
Comment 24 User image Albert Zeyer 2011-03-14 06:58:21 PDT
Curios, what is the state here? I actually only need to get the URL of the front window. This should be quite trivial on the Firefox site to be implemented. Why isn't it?

I guess this would maybe take an hour or so to be implemented for someone who is not experienced with the Firefox/Mozilla source (excluding the time to setup the build environment -- no idea how complicated that is) and maybe about 5-10 minutes for someone who is.

I would look at this (at least for just getting the URL) if I would know that this would be applied soon after to the stable branch and will got into FF4. (Otherwise it would be no use for me.)

But mostly I am curios: Why haven't it been done already? Can someone give some technical details?

Note You need to log in before you can comment on or make changes to this bug.