Closed
Bug 31802
Opened 25 years ago
Closed 25 years ago
unable to type in Location field after visiting secure site
Categories
(SeaMonkey :: UI Design, defect, P3)
Tracking
(Not tracked)
People
(Reporter: bugzilla, Assigned: radha)
References
()
Details
(Keywords: platform-parity, regression)
this is very weird --it happened on my machine (hopey.mcom.com), running redhat
linux (kernel v2.2.12-20) --when using either AfterStep or Enlightenment as
window managers. found while using the beta (non-trunk) optimized commercial
bits 2000.03.13.19-nb1b.
to repro:
1. type the above url, ie, "junruh" into the Location textfield.
2. hit Enter key. you might get a dialog saying that https is not a registered
domain --this a known regression bug (dunno the number, alas).
3. try to go to another page by typing a URL in the Location field.
result: cannot enter text into the Location field.
workaround: use the Open Web Location dialog. however, this is still a
regression.
Reporter | ||
Updated•25 years ago
|
Keywords: pp,
regression
Comment 1•25 years ago
|
||
the warning 'https is not a registered protocol' is not a bug, because those are
mozilla builds that don't contain security
also, I think these builds didn't get packaged correctly, so I'm not sure any
testing with these builds are valid
Comment 2•25 years ago
|
||
sarah informed me that she was using netscape commercial bits, so I stand
corrected :-)
Reporter | ||
Comment 3•25 years ago
|
||
dang. going to a secure page no longer causes the Location field to be
inaccessable. tested w/2000.03.16.05 opt comm bits (beta1 branch).
but i've managed to find another way to make the Location field inaccessible:
1. open another browser window.
2. in Location field, double-click to select all the contents.
3. overwrite current contents by typing www.supersnail.com, then hit Enter key.
4. click on link for Comix Creators.
5. once that page loads, go to the Location field to type something else.
result: you can't. the I-bar cursor is there when you mouseover, but unable to
click into field, or edit it...
i wonder if i should just mark this one WFM, then open another bug...? would
rather not morph this one, but am not sure if the failure am seeing now is
related to the original problem...
Summary: unable to type in Location field after visiting secure site → unable to type in Location field after visiting secure site/opening new browser?
Reporter | ||
Comment 4•25 years ago
|
||
hokay, am gonna split the latter problem into another report, bug 32120. mark
wfm.dup as needed, tho'... :-)
Summary: unable to type in Location field after visiting secure site/opening new browser? → unable to type in Location field after visiting secure site
Comment 5•25 years ago
|
||
I visited "https://junruh", browser around and then went to another site. But I
did not see the cursor problem. Used today's linux commercial beta1 bits.
Reporter | ||
Comment 6•25 years ago
|
||
just spoke with shrir about this --i can repro this *erratically* when i enter
http://junruh (argh)--but i cannot repro it when entering https://junruh...
methinks it might be best to simply make this a dup of 32120. but if anyone
thinks this is a seperate issue, do lemme know.
*** This bug has been marked as a duplicate of 32120 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•