Skip to main content

damn you javascript

I have be using more javascript and css than I would like recently, but the power is amazing. My most recent revelation was that "read only" is for suckers, and using "disabled" is a better way to protect elements in forms from user access.  the main reason is because you can set disabled=[true|false] on any input:  text, select, checkbox etc.

I used a css selector to make the disabled elements look a little nicer:

input[disabled="disabled"] {color:black; background-color:gray;}

So now I could have an edit button.  Click the edit button and

Pseudocode:
for (all elements in form){
    element.disabled=false;
}
click the cancel button and:
for(all elements in form){
    element.disabled="disabled";//don't set true because of css selector
}


That actually didn't work. SCREW YOU JAVASCRIPT. However I made a css "formActive" and "formInactive"

.formInactive{
    padding: 1px 0px 1px 0px;
    border-width: 0;
    background-color:transparent;
    disabled:true;
}


.formActive{
    border-style: solid;
    border-width: 1px;
    border-color: #036399;
    background-color: AliceBlue;
    padding: 1px 0px 1px 0px;
    disabled: false;
}
So now I just loop through and change the styles for the elements:

enable:
for (i = 0; i < theForm.elements.length; i++) {
    myElement = theForm.elements[i];
    if (myElement.className == 'formInactive') {
        myElement.className = 'formActive';
    }
    else{
        if(myElement.disabled){
             myElement.disabled = false;
        }
    }
}
disable:
for (i = 0; i < theForm.elements.length; i++) {
    myElement = theForm.elements[i];
    if (myElement.className == 'formActive') {
        myElement.className = 'formInactive';
    }
    else if(myElement.disabled = false){
        myElement.disabled=true;
    }
}
Sweet eh? The problem though is that I forgot to reset the form. So I went back into the cancel button loop and added "form.reset()"

No reset happened. javascript console had an error : "no such method form.reset()"

SCREW YOU JAVASCRIPT!!!!

Very irritating. To make a long story short, if you have an element ANYWHERE ON THE FRIGGIN PAGE named reset, you can't call the reset() function. Damn weakly typed languages. Changed the element name from reset to resetter, and everything worked.

Comments

Post a Comment

Popular posts from this blog

 In software engineering, accumulating code behind a release wall is akin to gathering water behind a dam. Just as a dam must be built higher and stronger to contain an increasing volume of water, the more code we delay releasing, the more resources we must allocate to prevent a catastrophic flood—major bugs or system failures—while also managing the inevitable trickles—minor issues and defects. Frequent, smaller releases act like controlled spillways, effectively managing the flow of updates and reducing the risk of overwhelming both the system and the team. The ideal of ci/cd may not be achievable for all teams, but smaller and faster is always better.
Post a Comment
Read more

Preventing accidental large deletes.

Instructions for Developers on Using the safe_delete Stored Procedure To enhance safety and auditability of delete operations within our databases, we have implemented a controlled deletion process using a stored procedure named safe_delete . This procedure relies on a temporary table ( temp_delete_table ) that lists complete records intended for deletion, not just their IDs. This approach helps prevent accidental deletions and provides a traceable audit log of delete actions. Why We Are Doing This Controlled Deletions : Centralizing delete operations through a stored procedure reduces the risk of erroneous or unauthorized deletions. Auditability : Using a temporary table to store complete records before deletion allows for an in-depth review and verification process, enhancing our ability to confirm and audit delete operations accurately. Security : Restricting direct delete permissions and channeling deletions through a specific proced...
Post a Comment
Read more

October is Cyber Security Month

The President has declared October as Cybersecurity month.  It's not a bad idea -- just like you change the batteries in your smoke detectors once a year, maybe you should review your electronic vulbnerabilities? My top ten security tips: 1) Change your passwords.  You've had them too long, you use the same password in too many places.  Somewhere someone has hacked a site that has your username and password in plain text.  Now they are getting ready to try that username/password somewhere else.  Beat them to the punch. 2) Use a safe browser.  That means anything that's not Internet Explorer.   I prefer chrome. 3) Use 2 step verification for your email account.  If your email doesn't provide 2 step authentication consider switching. 4) Get a free credit report  and review it.  You are entitled to one free report a year.   BE VERY CAREFUL!  There are man scam sites that offer free credit reports.  Go through the s...
16 comments
Read more