Closed Bug 94529 Opened 23 years ago Closed 22 years ago

Insert key on a textbox should start over-type mode

Categories

(Core :: DOM: Editor, enhancement, P5)

Product:
Core
Component:
DOM: Editor
Platform:
x86
Windows 98
Type:
enhancement

Tracking

()

Status:
VERIFIED DUPLICATE of bug 38415
Milestone:
Future

People

(Reporter: SkewerMZ, Assigned: Brade)

References

Details

(Keywords: helpwanted) 

Procedure: Type "abc" and put the cursor before the "b". Press the insert key
and type "x".

Expected: Textarea now reads "axc".

Actual: Textarea now reads "axbc".

Build: 2001080508 Win98
this behavior did not exist in 4.x versions, and was/is not scheduled for this
version either. am going to put this into future, add helpwanted, etc. letting
joe  make the final call
Assignee: beppe → jfrancis
Severity: minor → enhancement
Keywords: helpwanted
Priority: -- → P5
Target Milestone: --- → Future
!
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
verified.
Status: RESOLVED → VERIFIED
Question. Why not at least leave it open to suggestion as a future/enhancement?
Will reopen if not given reason not to.
Reopening bug.
Status: VERIFIED → REOPENED
Resolution: WONTFIX → ---
-> nobody@mozilla.org
Assignee: jfrancis → nobody
Status: REOPENED → NEW
Kathy, what do you wanna do with this one ?
Assignee: nobody → brade
-->WontFix

The Composer team has no intention to implement this functionality.  We have many 
more important bugs to fix and features to implement.  For example, I think 
"Publishing" feature would be more widely used than this feature and should be 
implemented first... I could name many other features... this is not important to 
Composer.
Status: NEW → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → WONTFIX
brade: Are you opposed to a volunteer/non-netscape fixing this bug?
Yes, I would try to encourage that person to work on a more useful feature or 
bug.  Surely there are other things you'd prefer to see in Composer before this 
gets implemented...

verified.
Status: RESOLVED → VERIFIED
This seems like a very nice feature to have... I really don't like that
"WONTFIX" being used on it. Couldn't we consider a more optimistic resolution,
such as LATER?
Think of "Later" as deprecated; it's not really used nor should it be.
In some sense, "later" is like the Future milestone.  In this case, we are saying 
that no one has any interest in implementing or assisting in this feature so we 
won't fix it.  We don't think it's worth the time/resources/bloat.  Type-over is 
dead.  Sorry.

CC: Hixie- This is the bug I told you about. It was WONTFIXed by a few Netscape
techs for invalid reasons.
It was wontfixed by the module owners because they don't want the feature
implemented. That is their right. (Their affiliation is totally irrelevant.)
I'm sorry, but I must once again protest the WONTFIX resolution and reopen the
bug, after finding out about bug 156979. It is insane for anyone to suggest that
over-type will cause bloat while marquee support is added to the browser like this.

I want a good, long, convincing explanation for why bug 156979 is acceptable but
this is not before this is WONTFIXed again (or INVALID or other stupid resolutions).

If assignee doesn't like this, please reassign the bug to nobody@mozilla.org and
don't touch it anymore.
Status: VERIFIED → REOPENED
Resolution: WONTFIX → ---
This has nothing at all to do with the marquee tag so that argument doesn't
stand for editing issues.

-->WontFix

The Composer team has no intention to implement this functionality or take a
patch that does implement this fix.  We have many more important bugs to fix and
features to implement.  

As for an argument, I don't believe one is necessary.  Please notice that this
bug has no duplicates and no votes which means this is very unimportant to those
who do any editing.  There is no argument to have this functionality available.
Status: REOPENED → RESOLVED
Closed: 23 years ago → 22 years ago
Resolution: --- → WONTFIX
verified.
Status: RESOLVED → VERIFIED
Your conduct is very unreasonable and not in the best interest of the Mozilla
project. I find it very insulting that you cannot at least provide me with a
reasoning for this unilateral decision.
*** Bug 150043 has been marked as a duplicate of this bug. ***
brade: an argument against this feature *is* necessary for wontfix, because it's
a consistency issue with the Windows platform.  (Note that notepad does not have
an overwrite mode in 98 or XP, weakening the consistency argument.)

I've entered overwrite mode in other Windows apps intentionally approximately
once, and about 30 times accidentally.  Many of those times, I didn't notice
until I had typed over a large amount of text that I did not intend to delete. 
Overwrite mode is too easy to trigger accidentally, provides very little
feedback, and is not useful except for ascii art.

I vote for wontfix.
Some counter-arguments (you can tell I *really* want this feature):

Coding done in the browser (e.g. on-site HTML editors) would be greatly
simplified with over-type.

It won't be confused with insert mode if we draw the cursor the proper way; a
line for insert mode, a box for over-type.
Blocks: 164421
I think that we should reopen this bug and set REMIND or leave it open with TM:
Futur.
And to Comment #18 - over-type is a basic thing in every UI working with text! 
Brade will just close it again; he doesn't want this bug fixed. He prefers for
the browser to behave incorrectly.
this is really a duplicate bug
Status: VERIFIED → REOPENED
Resolution: WONTFIX → ---
dupe

*** This bug has been marked as a duplicate of 38415 ***
Status: REOPENED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → DUPLICATE
verify dupe
Status: RESOLVED → VERIFIED
No longer blocks: 164421
You need to log in before you can comment on or make changes to this bug.