As a result of recent changes in Xmarks you may experience some problems if you're also a NoScript user.

Xmark's login dialog and setup wizard ask you to "Allow JavaScript on", or directly come out broken as HTML source. You cannot exit the dialog (the browser seems stalled), and even if you manage to, you discover that allowing or even the whole does not help.

The solution

  1. Use the "Esc" key to exit the dialog
  2. Click the NoScript icon and look in the "Recently blocked sites" submenu.
  3. Select Allow, Allow or both (whathever you find there).

Alternatively, you can open NoScript Options|Whitelist and manually allow and Looks like the Xmarks folks overlooked the need of allowing the latter.

Extensions developers!

More in general, extensions developers who need some web site to be allowed in NoScript for their extension to work, may want to use some code like this:

if (";1" in Components.classes) {
  let ns =  Components.classes[";1"]
  let myWhitelist = ["", ""]
    .filter(function(s) {
      return !ns.isJSEnabled(s);
  if (myWhitelist.length > 0) {
    let prompt = Components.classes[";1"]
    if (prompt.confirm(null, "Xmarks Permission Request",
       "Xmarks needs to add\n" + myWhitelist.join(" and ") +
       "\nto your NoScript whitelist.\nProceed?")) {
       ns.setJSEnabled(myWhitelist, true);

3 Responses to “Xmarks and NoScript Compatibility Woes”

  1. #1 Spawn says:

  2. #2 Peter B. P. says:

    Thanks for this solution!

  3. #3 Uakko says:

    Ciao Giorgio, scusa se scrivo in questo post, ma volevo chiederti perche quando clicco su "Permetti temporaneamente tutta la pagina" devo ripeterlo 2 o 3 volte prima che l'icona del divieto sulla S nella barra di stato scompaia del tutto.

Bad Behavior has blocked 576 access attempts in the last 7 days.