Closed
Bug 544657
Opened 15 years ago
Closed 15 years ago
move urlbar emptytext code to the urlbar binding
Categories
(Firefox :: Address Bar, defect)
Firefox
Address Bar
Tracking
()
RESOLVED
FIXED
Firefox 3.7a2
People
(Reporter: dao, Assigned: dao)
Details
Attachments
(1 file)
7.14 KB,
patch
|
Gavin
:
review+
|
Details | Diff | Splinter Review |
Just like the binding manages the other browser.urlbar.* prefs. No reason to clutter browser.js with this.
Attachment #425639 -
Flags: review?(gavin.sharp)
Updated•15 years ago
|
Attachment #425639 -
Flags: review?(gavin.sharp) → review+
Assignee | ||
Comment 1•15 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 3.7a2
Comment 2•15 years ago
|
||
Assignee | ||
Comment 3•15 years ago
|
||
I don't know. I couldn't figure it out on the dashboard and graph.html doesn't give me graphs.
The emptytext is being set after a timeout in the xbl constructor, while it used to be set after a timeout from a load event listener. Since the xbl constructor precedes the load event, I guess I could try to increase the timeout, although that will cause problems with browser_bug495058.js.
Comment 4•15 years ago
|
||
(In reply to comment #3)
> I don't know. I couldn't figure it out on the dashboard and graph.html doesn't
> give me graphs.
The first thing graph.html does is load a 7mb file with a list of 42000 test machines... maybe you just need to be more patient ;)
> The emptytext is being set after a timeout in the xbl constructor, while it
> used to be set after a timeout from a load event listener. Since the xbl
> constructor precedes the load event, I guess I could try to increase the
> timeout, although that will cause problems with browser_bug495058.js.
Ah, so it's just moving the goalposts, and the regression is an artifact of the arbitrary point at which onload fires?
Assignee | ||
Comment 5•15 years ago
|
||
Well, setting the emptytext earlier could actually result in more work.
Assignee | ||
Comment 6•15 years ago
|
||
It looks like bug 547224 solved the perf issue.
Comment 7•15 years ago
|
||
Yay!
You need to log in
before you can comment on or make changes to this bug.
Description
•