Addresses can be issues, too. I live at an address that looks like this (numbers changed for privacy, but the appearance is the same):
44-1234 Mauna Lani Point Dr
in Hawaii. This is the official USPS address. This form of hyphenated street number is common for addresses in Hawaii, mostly found outside of cities and built-up areas.
Websites that validate addresses against the USPS system are OK with this address. But others…
Many websites don’t accept the hyphen. (Not that they explain why; usually some cryptic error message.)
Also there are a lot of letters here. A lot of forms don’t give enough space so we have to abbreviate it or use the second address line (if offered).
Then there are companies that decide to really abbreviate this. American Express (a company you’d think would know better) sends our statements to:
44-1234 MAN LAN PT D
Someone at American Express saved a lot of precious bytes by coming up with this abbreviation! (And fortunately, someone here at the Post Office has figured out how to interpret it.)
Interesting. Lowe’s has no trouble with my domain (***.info), but I can think of several websites (including a US… airline!) that still can’t deal with it, even though I had used the exact same email address to sign up for an online account year ago. So I decided not to fly with that airline anymore. Rolling, rolling, rolling…
When the keyboard command for paste doesn’t work, try right-clicking in the password field and select paste from the contextual menu. Many times this works.
Most likely Discourse removed the JavaScript. I don’t know what the risk might have been for people receiving it by email but it would definitely be risky for the site to accept unvetted JavaScript to present in the web forum.
If you changed it to make it non-operational, like removing the opening and closing angle brackets, it might not be stripped but then again it still might, it depends on how Discourse identifies the script. If you reply to this thread on the web, especially if you use the Preformatted Text styling button for it, the reply form may automatically render the bookmarklet safe but visible.
@rogerd.parish, the best way to insert code in this forum/mailing list is to use the Markdown delimiters for code blocks: either start a line with four spaces, or use backticks (`):
This is a code block created by putting four spaces at the beginning of the line.
And you can put code inline by surrounding the code by backticks.
/*
Following code overrides the disabling of onpaste methods.
Based on code from:
http://prioritized.net/blog/re-enabling-password-pasting-on-annoying-web-forms/
Note: Only works in Chrome & Safari
*/
var inputs=document.getElementsByTagName('input');
for(var i=0;i<inputs.length;i++)
{
if(inputs[i].getAttribute('type').toLowerCase()==='password')
{
inputs[i].onpaste = function(e) {
// only Chrome and Safari support clipboardData access on event object
// see http://codebits.glennjones.net/editing/getclipboarddata.htm
if (e.clipboardData != undefined && e.clipboardData.getData != undefined)
{
this.value = e.clipboardData.getData('text/plain');
}
return false;
}
}
}
[Edited to use preformatted (four-space prefix) instead of blockquote (angle bracket prefix). -Adam]
About 15-20 years ago the Postal Service changed Zip codes for some Boston suburbs, so 021xx became 024xx. It caused no end of problems because no software in the world had considered the possibility that a few postal codes would be changed. I had thought the problem had finally died until a couple of weeks ago when I tried to make reservations on JetBlue and it refused to accept the Zip code. I gave up in disgust, went off to do something else, then tried restarting the Mac and was surprised when it worked.
Nowadays a more common problem with zip codes is software that automatically deletes leading zeroes before passing the data along to the zip code interpreter, changing my 024xx zip code to 24xx, which is rejected.
Thank you, I’ll do that. I tried Will_M’s advice (above) about dom.event.clipboardevents.enabled in Firefox, but it disabled pasting into ordinary text fields, which is a bigger drawback than the occasional password problem.
Thanks Roger! I’ll keep that for when I return to Safari, as I inevitably will. I guess it might work with Brave, too. It looks as if it operates only on password fields, which would avoid the problem I mentioned above with ordinary text fields.
I have a reluctance to setup automatic billing tied to a bank account to this day after what Bellsouth did to me 20 years ago.
I was one of the first in the area to get DSL before 2000. My installer was in the first class and I was his 5th install.
Now a few months later I logged into the Bellsouth site and paid my current phone bill. Something like $120.45. I made a mistake and typed something like 120.455. The wib site accepted my entry and didn’t complain. That bank account was
over drawn a day or so later. Long story short the Bellsouth software would take whatever you typed remove the decimal point and assuming the last 2 digits were the cents ship the data off to the 1958 or so billing system. Which debited my bank account by
$1204.55.
I called them up. Guess what, customer service then and in many cases now, has no idea how to deal with such a processing error. They kept putting me off discussing things like “we’ll just keep the money and let your bills catch up” or
how about we look into this and give your money back in a month or few if we think you might have a point.
Anyway (now the DSL is relevant) I got on the Bellsouth DSL support NEWSGROUP and asked for help. Some of the IT management walked over to billing (all in Atlanta and in the same building it turned out) and yelled. I got my money back in
a about a week. Even though promised in a few days.
That might have been when there was a push by the Merchant Customer Exchange to create their own payment system called CurrentC. Apparently, MCE would not let retailers have a competing system.
I’ve seen this too. The software is typically using a numeric field for the Zip code instead of a string field, which is more correct.
Using a numeric field means you need to jump through hoops when printing (e.g. insert leading zeros) and when handing them off to third-party validation software. It also makes you implement all kinds of ugly hacks to support 9- and 11-digit Zip codes (which include hyphens when properly printed).
When they first stopped it, they still had Samsung’s payment system. Just nothing for Apple. I never paid attention after that. I don’t go there often and just have to remember to bring my wallet in, which is a pain on its own.
They don’t accept Google or Samsung Pay either. Apple Pay was the first mobile credit service on the block, and Home Depot accepted it for a while only at the stores they had wired up for contactless payment. Then Home Depot, Walmart and some others developed a mobile payment partnership with PayPal. Walmart never signed on with Apple or Google Pay to begin with.
I think CVS has been part of the Home Depot/Walmart contactless deal since day one. They began accepting Apple and Google Pay about a year or two ago, probably because PayPal didn’t generate enough business on its own.
I thought CVS had Apple pay initially, then it went to magically paying inside it’s own app still using the card I had in Apple Pay? I’m not sure how that worked, but not long ago payment through the app stopped and I use Apple Pay again.
I used Apple pay on my laptop for the first time this morning, that was interesting!
