Closed
Bug 356267
Opened 18 years ago
Closed 14 years ago
Extension components not excluded by "chrome" filter
Categories
(Other Applications Graveyard :: Venkman JS Debugger, defect)
Other Applications Graveyard
Venkman JS Debugger
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bugzilla-mozilla-20000923, Assigned: rginda)
References
Details
(Whiteboard: [vnk-0.9.88][vnk-0.9.88.1])
Attachments
(4 files)
136.05 KB,
patch
|
Details | Diff | Splinter Review | |
9.57 KB,
patch
|
Gijs
:
review+
|
Details | Diff | Splinter Review |
9.30 KB,
patch
|
Details | Diff | Splinter Review | |
2.54 KB,
patch
|
mnyromyr
:
review+
|
Details | Diff | Splinter Review |
The Venkman code to exclude "chrome" files is Mozilla 1.2 code. It just excludes anything in the same directory as venkman-service.js. It's time to fix that. :)
Reporter | ||
Updated•18 years ago
|
Whiteboard: [0.9.88]
Reporter | ||
Updated•18 years ago
|
Whiteboard: [0.9.88] → [vnk-0.9.88]
Reporter | ||
Updated•17 years ago
|
Status: NEW → ASSIGNED
Reporter | ||
Comment 1•17 years ago
|
||
This also fixes the chrome filter to work correctly (toggling after starting). Will attach -w diff for review.
Reporter | ||
Comment 2•17 years ago
|
||
Attachment #277137 -
Flags: review?(shaver)
Reporter | ||
Updated•17 years ago
|
Assignee: silver → rginda
Status: ASSIGNED → NEW
QA Contact: caillon → venkman
Comment 3•17 years ago
|
||
Comment on attachment 277137 [details] [diff] [review] diff -w version of previous attachment r=me, but: * I'd prefer to hold off on checking this in if we can find a timely solution to bug 358286. * The back of my mind is wondering whether it makes any sense at all to cache the "is this file chrome or a component" info somewhere - given the component dir thing is O(n*m) (for n JS/HTML/XUL files and m component dirs)
Attachment #277137 -
Flags: review?(shaver) → review+
Comment 5•14 years ago
|
||
James, the file: stuff is fixed in current HG Vnk now. I attempted to un-bitrot your patch, but I ran into some issues with rec.show() (in venkman-views: Internal error processing hook “scripts:chrome-filter”. TypeError: rec.show is not a function @ <chrome://venkman/content/venkman-views.js> 1079 Any clue what that's about?
Attachment #466115 -
Flags: review+
Updated•14 years ago
|
Attachment #466115 -
Flags: review+
Reporter | ||
Comment 6•14 years ago
|
||
It should be rec.unHide().
Comment 7•14 years ago
|
||
(In reply to comment #6) > It should be rec.unHide(). Great, that works. I've commented out the if ("parentRecord" in rec) check, too, as that meant changing back from not showing to showing them didn't work. I tested that change with expanded scripts, seemed to all be just fine, so committed that. Thanks a lot! (changeset: 654:b63d7bb88a0f)
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 8•14 years ago
|
||
Of course, I didn't take into account that Fx 4 would nuke this out of orbit because ComsD and friends have been removed, so these directory service calls throw exceptions instead. Great. Patch in a second.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 9•14 years ago
|
||
Attachment #467062 -
Flags: review?(mnyromyr)
Comment 10•14 years ago
|
||
Comment on attachment 467062 [details] [diff] [review] Fix detection on trunk / Moz 2.0 r=me with bracing style fixed.
Attachment #467062 -
Flags: review?(mnyromyr) → review+
Comment 11•14 years ago
|
||
(In reply to comment #10) > Comment on attachment 467062 [details] [diff] [review] > Fix detection on trunk / Moz 2.0 > > r=me with bracing style fixed. Checked in with braces fixed, changeset 661:db6bde58e48d
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Whiteboard: [vnk-0.9.88] → [vnk-0.9.88][vnk-0.9.88.1]
Updated•6 years ago
|
Product: Other Applications → Other Applications Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•