133706 - [RFE] On New Browser event driven script execution (startup macro)

Status: RESOLVED EXPIRED

(SeaMonkey :: UI Design, enhancement)

Description

[Chris Lee]

It would be handy to have an event at start of any mozilla component, but
browser is my piority, that would allow a function to be called from a
userscripts.js file that could be used to open web pages in various tabbs or
windows, open a mail folder and colect mail etc.
That way users can edit their startup sequence using something allong the lines
of the 'UI DOM' to accomplish what they want to do.
a few supplied functions for common tasks would be nice like:
openDocument('http://mozilla.org',tab)
openMail('MyAccount','inbox')
GetMail('Myaccount')

An additional enhancment to that is to add a menu to the UI that lets you create
an event and then trigger it thus runing a specified function, giving macro
mozilla the power of macros.

Comment 1

[Asa Dotzler [:asa]]

maybe it would be nice. I'm not implementing it. 

Comment 2

[timeless]

if someone said "that's already possible today", what would you say?

Comment 3

[Chris Lee]

Great, Where do I put the code and how do I assign it to an event such as 'new
browser opened' or 'user scheduled event 01' etc.
Then also what handy pre-written functions are available? where are they documented?

Last but not least I would say if the above is possible then lets change this
RFE to creat a UI to allow for creation/scheduling of events and linking them to
code in the appropriate place.

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420