noscript.fixURI still effectual?
Posted: Thu Jan 28, 2010 4:14 am
noscript.fixURI still effectual, less effectual?
noscript.fixURI
noscript.fixURI.exclude
.exclude = ""
backslashes are encoded, not what I want
.exclude = "reg"
backslashes are left alone, I'm happy
but what about "spaces", which are still encoded as %20?
how can I end up with "reg:hklm\software\realtek semiconductor"?
As I recall, when fixURI was first implemented, "spaces" were not an issue.
Don't know if they are now due to changes in NoScript or changes in Mozilla?
(Don't you wish later Mozilla versions still returned meaningful dialogs like these!)
<They call this progress ... phewy! I'll lay the blame on Firefox.>
noscript.fixURI
noscript.fixURI.exclude
.exclude = ""
backslashes are encoded, not what I want
.exclude = "reg"
backslashes are left alone, I'm happy
but what about "spaces", which are still encoded as %20?
how can I end up with "reg:hklm\software\realtek semiconductor"?
As I recall, when fixURI was first implemented, "spaces" were not an issue.
Don't know if they are now due to changes in NoScript or changes in Mozilla?
(Don't you wish later Mozilla versions still returned meaningful dialogs like these!)
<They call this progress ... phewy! I'll lay the blame on Firefox.>