Closed Bug 31115 Opened 26 years ago Closed 26 years ago

Problems with plain text field in Netscape phonebook

Categories

(Core :: DOM: Editor, defect, P3)

Product:
Core
Component:
DOM: Editor
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED WORKSFORME

People

(Reporter: bijals, Assigned: Brade)

Details

(Whiteboard: [PDT+] w/b minus on 03/10)

Steps: 1) Go to phonebook in Navigator 2) Type a name and hit the search botton Actual Results: You get an error message saying not string supplied, but you can see what you typed in the name text field. Expected Results: Phone book works properly. Build Date/Platform: Late 3/9/00 build on NT
I am having problems with other forms such as scopus where the caret does not appear anywhere and what I type does not get reflected.
Keywords: beta1
I am testing this on the commercial bits on Mac (2pm build yesterday). I don't see the problem that Bijal is describing (initially). I see 2 dialogs telling me that I am entering a secure document. The comments from Bijal at 19:06 sound unrelated to "getting an error message" in the original description. Can anyone else reproduce this problem? Is it windows-specific?
With the 3/9 linux commercial build, I see what Kathy sees: two dialogs about entering a secure document (has anyone filed a bug on that?), then the correct phonebook page.
Is this only with phonebook? Sujay, try on all platforms...let us know if mac too?
Whiteboard: [NEED INFO]
using 3/9 build: windows works after the 2 security dialogs mac gives me this error: "https is not a registered protocol" linux crashes
Was your mac build a mozilla or commercial build? https is only available in the commercial build, of course.
Putting on PDT+ radar for beta1.
Whiteboard: [NEED INFO] → [PDT+] w/b minus on 03/10
I don't understand this bug at all. It is very unclear (as my comments yesterday indicated). The only thing I see here is that Sujay was able to crash a linux build. Is that why this is PDT+? It's not clear this is even an editor bug. Bijals and PDT group: please comment.
yes mac build was mozilla build...
I *think* it was PDT+ because there was an example of an https page not working on two platforms. Seems like what it really needs is for someone to investigate it. If the real bug is small or rare to see, then that analysis should be in the bug, and the PDT+ removed for reevaluation.
What Sujay saw looks like two different pp bugs, neither of which are obviously related to the edit field or other editor code, both of which sound potentially serious and should be investigated. But this bug is on the edit field on that page, and no one seems to be able to reproduce that bug. Should we assume it no longer exists, and morph this into one of the other two bugs? Or close this as worksforme and open two new ones? Sujay, are you still seeing the crash? It works for me on linux (after the two dialogs) with the 3/9 am build. I went to "pb" via the urlbar and typed "bijals", what did you do?
doesn't crash anytmore on linux...mac is fine also...commercial...
Bij is out today; resolving this bug as worksforme
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → WORKSFORME
verified on all 3 platforms using commercial 3/10 builds.
Status: RESOLVED → VERIFIED
Could not reproduce it with Monday's build so worksforme also.
setting to an approximate milestone so it can be off of the no TFV list
Target Milestone: --- → M15
You need to log in before you can comment on or make changes to this bug.