show busy cursor when pasting and other slow actions

RESOLVED EXPIRED

Status

SeaMonkey
Composer
--
enhancement
RESOLVED EXPIRED
16 years ago
3 years ago

People

(Reporter: timeless, Unassigned)

Tracking

({helpwanted, polish, pp})

Trunk
x86
Windows 2000
helpwanted, polish, pp

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [ui], URL)

(Reporter)

Description

16 years ago
[5/29-04 w32 talkback]
steps:
copy contents of nsTableFrame.cpp (4290 lines)
go to a page that has a text area (bugzilla comment field). paste.
[hover over reload button]

On my p2/450 w2k it took 62 seconds and I had the Ibeam for the entire time.

expect: busy cursor since I can't click any of the nav buttons.

Comment 1

16 years ago
I also noticed this during performance testing...I've included a URL
above that I used.

I also see the same problem when opening a file like the one above.

Comment 2

16 years ago
When I paste huge amount of text using right-click pop-up menu, the menu stays
there and the world freezes over...

Comment 3

16 years ago
handing over to brade and cc charley -- I vaguely remember somebody saying 
something about not being able to do this
Assignee: beppe → brade

Updated

16 years ago
Keywords: polish
Priority: -- → P4
Whiteboard: [ui]
Target Milestone: --- → mozilla1.0.1

Comment 4

16 years ago
I see a watch cursor on my Mac build.  Is this a windows-specific bug?

Comment 5

16 years ago
Mac shows a watch cursor whenever it's away from the main event look for any 
length of time. So these kinds of bugs will differ across platforms.

Comment 6

16 years ago
This is a general problem needed in many places -- we don't use the busy
cursor at all!
Anyone know if and how we show a busy cursor?
Summary: show busy cursor when pasting → show busy cursor when pasting and other slow actions

Comment 7

16 years ago
Hrm, wouldn't it be better to fix pasting speed rather than indicate to the user
that we're just darned slow?

If I pasted a short amount of text, setting the cursor then re-setting the
cursor is going to slow it down slightly - you have to ask, why at all. I guess
you also run to risk of a bug creeping in that stops the mouse cursor being
turned back to normal again on quick pastes.

Comment 8

16 years ago
I doubt that setting the cursor twice would slow anything down much. It's O(1),
and it doesn't make a significant impact in any app I've seen.
(Reporter)

Comment 9

16 years ago
bryner says it's window.setCursor("wait");

Comment 10

16 years ago
If it's that easy, we definitely should do this before release!
Nominating for 0.9.2
Target Milestone: mozilla1.0.1 → mozilla0.9.2

Comment 11

16 years ago
1.0
Target Milestone: mozilla0.9.2 → mozilla1.0

Updated

16 years ago
Blocks: 91351

Comment 12

16 years ago
spam composer change
Component: Editor: Core → Editor: Composer

Comment 13

16 years ago
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 
(you can query for this string to delete spam or retrieve the list of bugs I've 
moved)
Target Milestone: mozilla1.0 → mozilla1.0.1

Comment 14

16 years ago
don't move bugs that are in the 1.0 dependency tree. sorry.

Target Milestone: mozilla1.0.1 → mozilla1.0

Comment 15

16 years ago
balancing milestones
Target Milestone: mozilla1.0 → mozilla1.1

Updated

15 years ago
Keywords: pp
Target Milestone: mozilla1.1alpha → Future

Comment 16

15 years ago
-->
note: it'd be better to address the performance issues before addressing this
(since more people will benefit from the perf fixes than those who would see the
cursor)
Assignee: brade → composer
Keywords: helpwanted
Product: Browser → Seamonkey
Assignee: composer → nobody
Priority: P4 → --
QA Contact: sujay → composer
Target Milestone: Future → ---

Comment 17

8 years ago
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
Status: NEW → UNCONFIRMED

Comment 18

8 years ago
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 19

8 years ago
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 20

8 years ago
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 21

8 years ago
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 22

8 years ago
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 23

8 years ago
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 24

7 years ago
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
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.