5 ms·
There appears to be a giant <div> on top of the entire website. It's the first non-comment child of <body>: <div id="forceDOMredraw"></div> With the CSS of:
by deathanatos 13y ago
There appears to be a giant <div> on top of the entire website. It's the first non-comment child of <body>:
<div id="forceDOMredraw"></div>
With the CSS of:
height: 3000px
width: 3000px
position: absolute
top: 0px
z-index: 50000
I do love arbitrary constants.
Killing it makes the site responsive. No idea what it's there for. I'm guessing that it should be moved by JS, but the JS is failing. There's a lot of these:
Uncaught TypeError: Property '$' of object [object Object] is not a function
Looks like jQuery isn't getting loaded, but that's probably because of:
[blocked] The page at 'https://corp.delaware.gov/paytaxes.shtml' was loaded over HTTPS, but ran insecure content from 'http://www.delaware.gov/CLF2012/js/jquery-1.5.1.min.js': this content should also be loaded over HTTPS.
So, yeah, no jQuery, no script, defunct page. The problems seem to be rooted in the fact that jQuery didn't load due to it being sent over HTTP, and not HTTPS; indeed, loading the page on HTTP causes things to appear to work.
Just don't use any security, and everything will work just fine. :-) This problem seems to cover the entirety of corp.delaware.gov, too.
Also, the 404's the article mentions,
GET https://corp.delaware.gov/undefined?1394573701086 404 (Not Found)
I doubt that the URL is supposed to have "undefined", but rather that JS has stabbed yet another dev in the back.
- jliptzin 13y agoOf course, the giant div! I use those all the time.
- antidaily 13y agoMaybe it's a loading spinner/graphic. Haha.
- joev_ 13y agoSo... on a crappier browser this would have worked? Heh, nice to know that they never bothered to open this in any modern browsers.
- deleted 13y ago[deleted]
- peterjmag 13y agoHe'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.
- zroger 13y agoLooks like the forceDOMredraw is defined in their offical "Common Look and Feel Version 3.0" docs. http://gic.delaware.gov/CLF30Glossary.pdf http://gic.delaware.gov/CLF30Glossary.pdf From the PDF: <div id="forceDOMredraw">: A div that forces the browser to redraw the content if it is displayed incorrectly.