How to fix “Error: NAMESPACE_ERR: DOM Exception 14” in Chrome

The only references I’ve found online are to an old bug in Chrome. Error: NAMESPACE_ERR: DOM Exception 14 I generated this with the following xpath expression generated by Firebug: id(‘content’)/x:div[2]/x:div[3]/x:div[1]/x:h2[2] This causes this javascript line to fail: document.evaluate(“id(‘content’)/x:div[2]/x:div[3]/x:div[1]/x:h2[2]”, document, null, XPathResult.ANY_TYPE, null) The fix is very simple: remove the namespaces – the “x:”, like so: […]

,

Fix to error installing “forever” for nodejs

After doing “npm install forever” in a VirtualBox instance you may get an error like the following. This is caused by running the install from a folder shared with the host machine. Certain file operations fail when crossing the machine/file system boundary in VirtualBox. npm ERR! error rolling back forever@0.8.5 Error: UNKNOWN, unlink ‘/vagrant/node_modules/forever/node_modules/winston/docs/winston/transports.html’ npm […]

Sample Greasemonkey Script in Chrome to process local files

The following script will fire an alert box for local files: // ==UserScript== // @name Matcher // @descriptions Match Local Files // @version 1 // @match file://* // ==/UserScript== alert(1); Save as “match.user.js”. Drop into a Chrome tab and you will be prompted to install. These are done per user profile. Each time you re-install […]