Bookmark problem with trunk again

[dhouwn]

Code: Select all

Error: n.parentNode is null
Source File: chrome://noscript/content/noscriptOverlay.js
Line: 1369

Code: Select all

Error: PlacesUtils is not defined
Source File: chrome://noscript/content/noscriptBM.js
Line: 89

Code: Select all

Error: uncaught exception: [Exception... "'[JavaScript Error: "PlacesUtils is not defined" {file: "chrome://noscript/content/noscriptBM.js" line: 89}]' when calling method: [nsIController::doCommand]"  nsresult: "0x80570021 (NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)"  location: "JS frame :: chrome://browser/content/places/controller.js :: goDoPlacesCommand :: line 1655"  data: yes]

(I know the first one might not be related, sounds strange nonetheless)

[Giorgio Maone]

With some serious troubles (all the Mozilla web infrastructure seems to be collapsing, maybe because Aza got slashdotted?) I managed to download today's trunk but couldn't reproduce anyway.
Step by step instructions?

[therube]

(This I suppose? Mozilla Preparing To Scrap Tabbed Browsing?)

[dhouwn]

Can't reproduce anymore.

On a side note, just had this here (probably because of some trunk bug):

Code: Select all

A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.

Script: chrome://noscript/content/Main.js:1562

[GµårÐïåñ]

The script busy that comes from NoScript has been around for a while and it comes and goes, leading me to believe its not ACTUALLY a NoScript fault but rather something else is hanging it up, probably because they are both trying to access the CAPS or some other chrome function simultaneously and one is superseding another. I have noticed that with different profiles and different extension configurations, it happens more, less or not at all. The unfortunate part is that to narrow down WHICH extension or which COMBINATION of extensions is causing this is no small feat as there is little to no logical sense in it allowing one to narrow the list. I have tried and tried and tried and when I think I have the right combination, bam the test to recreate fails to show a problem, so back to square one. It also doesn't help that Fx has no logical ordering of extensions in how they load and each profile is practically a crap shoot as to how they are ordered and therefore no way to even reproduce it always, for me deleting the extension files and letting it recreate OFTEN fixes the problem (its asinine I know but that's only way to get rid of it so far). This is why NoScript asserts itself last (thanks to the intelligence of the developer) but this sometimes forces it to take a backseat to something else that can be mucking up the place.