Closed Bug 890880 Opened 11 years ago Closed 6 years ago

computedStyle.js Error: NS_ERROR_NOT_AVAILABLE: Component is not available

Categories

(Other Applications :: DOM Inspector, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: philip.chee, Unassigned)

Details

Mon Jul 08 2013 20:26:23
Error: NS_ERROR_NOT_AVAILABLE: Component is not available
Source file: chrome://inspector/content/viewers/computedStyle/computedStyle.js
Line: 179
See Bug 407956 - Remove nsISupportsArray usage from nsITreeView.
Depends on: 407956
Is this why the !important indicator is broken?
Neil says this has nothing to do with Bug 407956

<NeilAway>	RattyAway: also Gijs needs to know that computed style doesn't have importance
RattyAway: the line of code is trying to retrive the actual computed value, so it's strange that it should say it's not available ;-)
No longer depends on: 407956
(In reply to Philip Chee from comment #3)
> Neil says this has nothing to do with Bug 407956
> 
> <NeilAway>	RattyAway: also Gijs needs to know that computed style doesn't
> have importance
> RattyAway: the line of code is trying to retrive the actual computed value,
> so it's strange that it should say it's not available ;-)

Oh, hum, yes, I would have known that had I thought about it more than I did. That said, I did suspect the lack of !important indicators was also related to the treeview stuff, but I guess that means it might not be and I should actually look into it; it's been bothering me.
Summary: computedStyle.js needs to be updated due to changes in the treeview API → computedStyle.js Error: NS_ERROR_NOT_AVAILABLE: Component is not available
Assignee: Sevenspade → nobody
Bulk close. This component is no longer supported or maintained.

https://bugzilla.mozilla.org/show_bug.cgi?id=1499023
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
Bulk close. This component is no longer supported or maintained.

https://bugzilla.mozilla.org/show_bug.cgi?id=1499023
You need to log in before you can comment on or make changes to this bug.