24489 - Spurious "failed to get the xpfe.dragdrop.enable" console message

Status: VERIFIED INVALID

(Core :: XUL, defect, P3)

Description

[John Morrison]

In the content:
  chrome/bookmarks/content/default/bookmarks.js
  chrome/navigator/content/default/navigator.js

 you have the following:

  var gDragDropEnabled = false;
  try {
    gDragDropEnabled = pref.GetBoolPref("xpfe.dragdrop.enable");
  }
  catch (ex) {
    dump("failed to get the xpfe.dragdrop.enable pref, assuming it is off\n");
  }

which (by default) is dumping the message to the console (at least on win32)

 Perhaps, you want to provide 'user_pref("xpfe.dragdrop.enable", false);' to
"prejs.js" by default to silence the spurious error. (Of course, you can't
do this retroactively, but to head off the inevitable, this should go in M13,
IMHO)

(And, maybe, this is just a typo on 'enable' vs. 'enabled')

Cheers, John

Comment 1

[Mike Pinkerton (not reading bugmail)]

is this really that important? it's a message to the console for pete's sake.
m20.

Comment 2

[John Morrison]

Nope. It's not important at all. It's obvious what's up if one takes a look.

I only mentioned this because past experience tells me that well-meaning
people _will_ file this a bug on this (more than once): "failed to get ..."
suggests something went (badly) wrong. Marking INVALID (after all, it's only
an interim thing). Sorry for the miscue.

Comment 3

[Mike Pinkerton (not reading bugmail)]

shrug. ok ;)

Comment 4

[shrirang khanzode]

Sorry for the spam, changing QA contact.

Comment 5

[timeless]

vrfy this code really doesn't exist.