3 ms·
He's been building web apps professionally for over 10 years, and he didn't think to right click somewhere (anywhere) and "Inspect Element"? That's the first th
by peterjmag 13y ago
He's been building web apps professionally for over 10 years, and he didn't think to right click somewhere (anywhere) and "Inspect Element"? That's the first thing I did on that page.
EDIT: That came off a bit more snarky (snarkier?) than I meant. To the OP: If you inspect the element, you can then delete it with the backspace/delete key to get to the link that you need, which ultimately leads to a separate subdomain that doesn't seem to exhibit this problem: https://delecorp.delaware.gov/eCorp/LoginAnnualReportsCLF https://delecorp.delaware.gov/eCorp/LoginAnnualReportsCLF
Don't be too quick to write the site off as "utterly dysfunctional". Any one of us could have made a similar mistake, and once you get past that glaring bug (which only appears on pages served over SSL), it's not bad for a state government site.
Perhaps you or someone else could get in touch with them to explain the issue? http://corp.delaware.gov/contact.shtml http://corp.delaware.gov/contact.shtml
- LeonidasXIV 13y ago> He's been building web apps professionally for over 10 years, and he didn't think to right click somewhere (anywhere) and "Inspect Element"? That's the first thing I did on that page. That's odd too, it was basically my first thought to inspect the element which used this pointless div and then tried deleting it. Total time spent: 15 seconds, less than reading this rant. (This is actually a habit I formed by getting rid of huge overlay ads that cover the page or try to force me to log in. No sir, I'll just have this node removed, thank you very much)
- mcv 13y agoI do the same thing. I wouldn't mind a plugin that automatically recognized crippling overlays and deletes them for me.