The default bug view has changed. See this FAQ.

Long script urls still confuse the debugger menulist

RESOLVED FIXED in Firefox 17

Status

()

Firefox
Developer Tools: Debugger
P2
normal
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: vporof, Assigned: vporof)

Tracking

12 Branch
Firefox 17
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

5 years ago
https://www.google.com/uds/api/gdata/1.10/208a907929e7936990d2bf48205aa8d8/core,mediarss,opensearch,geo,atom,threading,app,gdata,maps,gbase,finance,blogger,contacts,analytics,acl,calendar,default.I.js

is long.
(Assignee)

Comment 1

5 years ago
Yup, regression from patch in bug 771481 using sizetopopup="always" on the menulist.
(Assignee)

Comment 2

5 years ago
Created attachment 645712 [details] [diff] [review]
v1

Asking Rob in for review.
Attachment #645712 - Flags: review?(rcampbell)
Comment on attachment 645712 [details] [diff] [review]
v1

+const SCRIPTS_URL_MAX_LENGTH = 64; // chars

magic numbers! How did you arrive at 64? It's a nice power of two, a square and a cube. Its digits add up to 10. It has many extremely nice properties. But as a length of characters in a menu list?

+      ok(gDebugger.DebuggerView.Scripts.containsLabel(nanana + "Batman!" + ellipsis),
+        "Script (15) label is incorrect.");
+

haha. "wat"
Attachment #645712 - Flags: review?(rcampbell) → review+
(Assignee)

Comment 4

5 years ago
(In reply to Rob Campbell [:rc] (:robcee) from comment #3)
> Comment on attachment 645712 [details] [diff] [review]
> v1
> 
> +const SCRIPTS_URL_MAX_LENGTH = 64; // chars
> 

In addition to your valid arguments, 20 is dividable by 2 and 5, looks good and
(new Array(20).join(NaN) + "Batman!").length === 64.
Sorry.

In all seriousness, it feels like an acceptable number of chars to use and keep the menulist at an acceptable size. If you can think of other good algorithms to find a better number, please share.
nah, is cool.
Whiteboard: [land-in-fx-team]
(Assignee)

Comment 6

5 years ago
Created attachment 647971 [details] [diff] [review]
fail
(Assignee)

Comment 7

5 years ago
Comment on attachment 647971 [details] [diff] [review]
fail

Wrong bug!
Attachment #647971 - Attachment description: [land-in-fx-team] → fail
Attachment #647971 - Attachment is obsolete: true
(Assignee)

Comment 8

5 years ago
https://hg.mozilla.org/integration/fx-team/rev/3e77bd3b1596
Whiteboard: [land-in-fx-team] → [fixed-in-fx-team]
https://hg.mozilla.org/mozilla-central/rev/3e77bd3b1596
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → Firefox 17
https://groups.google.com/d/topic/mozilla.dev.tree-management/2jB_s0SpJ80/discussion

Regression :( Tp5 No Network Row Major MozAfterPaint increase 12.4% on Linux Fx-Team
------------------------------------------------------------------------------------
    Previous: avg 243.519 stddev 16.676 of 30 runs up to revision fcb3934935e2
    New     : avg 273.667 stddev 2.315 of 5 runs since revision 834a0c1ef40b
    Change  : +30.148 (12.4% / z=1.808)
    Graph   : http://mzl.la/QmD6Pd
I think from the graph it is evident that this regression is caused by the merge from m-c in changeset 8c63e260c4fa, which is conspicuously absent from the graph, but occurred right in the upward slope between revs f08a7ecc6d9f and 4f39921f782f.

This is way too low-level to be affected by debugger UI patches.
You need to log in before you can comment on or make changes to this bug.