Closed Bug 498841 Opened 17 years ago Closed 17 years ago

gURLBar.timeout shouldn't be set in BrowserStartup

Categories

(Firefox :: Address Bar, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 3.6a1

People

(Reporter: dao, Assigned: dao)

References

Details

Attachments

(1 file)

browserStartup is the wrong place for this, as the urlbar doesn't necessarily exist on startup.
Assignee: nobody → dao
Attached patch patchSplinter Review
Attachment #383654 - Flags: review?(gavin.sharp)
Summary: browser.urlbar.delay shouldn't be read & gURLBar.timeout shouldn't be set in browserStartup → gURLBar.timeout shouldn't be set in browserStartup
Summary: gURLBar.timeout shouldn't be set in browserStartup → gURLBar.timeout shouldn't be set in BrowserStartup
Comment on attachment 383654 [details] [diff] [review] patch While you're touching this code: >+ document.documentElement.getAttribute("chromehidden").indexOf("toolbar") != -1) { |toolbar.visible| would be so much easier to read...
(In reply to comment #2) > >+ document.documentElement.getAttribute("chromehidden").indexOf("toolbar") != -1) { > > |toolbar.visible| would be so much easier to read... IIRC that's not the same test, though I don't recall the distinction.
Attachment #383654 - Flags: review?(gavin.sharp) → review+
I don't think there's a difference... I recall researching this for bug 470051. A quick search now leads to this: http://mxr.mozilla.org/mozilla-central/source/dom/base/nsBarProps.cpp#165 http://mxr.mozilla.org/mozilla-central/source/xpfe/appshell/src/nsXULWindow.cpp#2093 I won't change it in this bug, though.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 3.6a1
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: