Closed
Bug 306061
Opened 19 years ago
Closed 19 years ago
locationbar is always empty. Can only use bookmarks and not type in a destination.
Categories
(Firefox :: Address Bar, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: thenrie, Assigned: benjamin)
References
Details
Attachments
(1 file)
|
2.38 KB,
patch
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050826 Firefox/1.6a1 I installed today's nightly trunk build for windows installer. When I launch Deer Park then the locationbar is blank. I then click a bookmark. The bookmark does take me to the correct url, however, the url never appears in the locationbar. Reproducible: Always Actual Results: blank locationbar Expected Results: I expect to see the url printed for the url that I am currently viewing.
Comment 1•19 years ago
|
||
Im pretty sure this is due to the checkins for bug 305767. There were some follow up patches that didnt make the nightly so hopefully the next build will be fixed.
Status: UNCONFIRMED → NEW
Component: General → Location Bar and Autocomplete
Ever confirmed: true
QA Contact: general → location.bar
| Reporter | ||
Comment 2•19 years ago
|
||
(In reply to comment #1) > Im pretty sure this is due to the checkins for bug 305767. There were some > follow up patches that didnt make the nightly so hopefully the next build will > be fixed. Could this also effect the option "ctrl+l", or from the file menu "open location"? I don't think that has worked in the last few nightly trunk images.
Comment 3•19 years ago
|
||
This issue still shows with the newer build. Copying in those involved in the other bug.
| Assignee | ||
Comment 4•19 years ago
|
||
Is there anything useful in the JS console? In particular, are there XML or CSS parsing errors of chrome files?
Comment 5•19 years ago
|
||
Should have looked there sooner really: Error: Expected declaration but found '#ifdef'. Skipped to next declaration. Source File: chrome://global/content/xul.css Line: 869 Error: Expected declaration but found '#endif'. Skipped to next declaration. Source File: chrome://global/content/xul.css Line: 872 Error: this.inputField has no properties Source File: chrome://global/content/bindings/textbox.xml Line: 0
Comment 6•19 years ago
|
||
I'm only seeing the this.InputField error in Comment 5. Here is an additional one I'm seeing: Error: this.inputField has no properties Source File: chrome://global/content/bindings/textbox.xml Line: 84
Comment 7•19 years ago
|
||
And this one: Error: event.target.rel has no properties Source File: chrome://global/content/bindings/tabbrowser.xml Line: 757 Also sad to notice that my extension External Application Buttons is non-functional. When I click one of the buttons I see an alert: "Type-Error: this.inputField has no properties"
| Assignee | ||
Comment 8•19 years ago
|
||
Argh... I don't know how I missed xul.css in this.
Assignee: nobody → benjamin
Status: NEW → ASSIGNED
| Assignee | ||
Comment 9•19 years ago
|
||
fixed on trunk
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
*** Bug 306081 has been marked as a duplicate of this bug. ***
Comment 13•19 years ago
|
||
For those wanting to fix this manually, it consists of going into %browserdir%/Chrome/toolkit.jar and editing the xul.css within searching for the c-style preprocessor blocks and deleting all the OSX and non-firefox sections as well as the preprocessor directives themselves.
You need to log in
before you can comment on or make changes to this bug.
Description
•