Closed
Bug 35976
Opened 25 years ago
Closed 25 years ago
url area becomes uneditable/clickable
Categories
(Core :: DOM: Editor, defect, P3)
Tracking
()
People
(Reporter: fstmm, Assigned: rubydoo123)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.12-20 i686; en-US; m14) Gecko/20000415
BuildID: 2000041508
After switching to different open windows, or attempting to click in the url
area while a page is loading, the url becomes uneditable and unclickable. The
black arrow remains when the mouse pointer is moved above the text field,
instead of becoming an I bar.
Reproducible: Always
Steps to Reproduce:
1. go to google.com
2. click on the 'about google' link
3. click on the url area
Actual Results: the url area is no longer editable
Expected Results: the url should become editable
this was the most reproducible using the above method, but changing web browser
windows appeared to have a similar, though less reliable effect. It can be
worked around by spawning a new window which will then have an editable url...
|
||
Comment 1•25 years ago
|
||
Build 2000041515, Win95B. I went to http://google.com, then clicked on the
About link. I clicked on the URL bar to edit the line, and it works for me.
|
||
Comment 2•25 years ago
|
||
fstmm@yahoo.com: What is your homepage? Does it consists of frames?
Does the bug still occur if you set your homepage to www.mozilla.org,
or start mozilla this way:
mozilla http://www.mozilla.org/
See bug 32120 and bug 31485 for known problems where the location bar
becomes unclickable. (The is the case if the homepage consists of frames
or has an <input type=password> form element in it.)
By the way, these known bugs seem to be linux only.
|
|
||
Comment 3•25 years ago
|
||
fstmm@yahoo.com writes:
> My homepage is http://google.com - it does not have
> any frames. Nor does it have an <input type =
> password> field, it does have a input field for
> submitting web query's.
>
> Testing with homepages mozilla.org and slashdot.org
> under build 20000417`` I cannot reproduce the
> result.
> Also, I cannot reproduce the result using google
> using build 20000417, so apparently it got fixed
> (unintentionally or no...)
Using google.com as homepage, I could reproduce the problem with
the method described in bug 31485, using builds
2000-04-18-16-M16 and
2000-04-18-11-M15.
(The M16 build does not show any Gdk-CRITICAL messages,
but the problem with the unaccessible location field
is the same.)
This simplified testcase is:
<html>
<head>
<title>Bug 31485 (google.com)</title>
<script>
function setFocus() {
document.f.q.focus();
}
</script>
</head>
<body onLoad="setFocus()">
<form name=f>
<input name=q>
</form>
</body>
</html>
Marking duplicate. I'm going to add the relevant information
to the other bug soon.
*** This bug has been marked as a duplicate of 31485 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•