RR (10,8): The number of rants is proportional to how bad something is
… multiplied by the usage frequency.
I still don't get why eSPACE must use a JavaScript form submit instead of a regular one… It doesn't provide any more speed, security, or convenience. Because I don't have *nus.edu.sg on my whitelist (while I do have KoL on my whitelist), the JS submit fails. I normally work around this by temporarily allowing scripts, or by submitting it using JavaScript from the location bar.
However, if you're like me, and you use eSPACE, have NoScript, and not have eSPACE on your whitelist, you'll quickly realise that the UI doesn't just use JS, it requires JS. In other words, the latter solution as stated above will be rather useless. There are only 5 accessible links, and one of them is a javascript: pseudo-URI.
The only plausible reason for the designers to use a JS submit is probably client-side verification. (Which, you can view-source and check for yourself.) Which is really useless, considering that the page is less than 10kB, which loads in less than 5 seconds even on dial-up. In other words, since they have to do server-side verification anyway, why not just do it all server-side?
And the multi-level nested tables (for layout) still suck.
I still don't get why eSPACE must use a JavaScript form submit instead of a regular one… It doesn't provide any more speed, security, or convenience. Because I don't have *nus.edu.sg on my whitelist (while I do have KoL on my whitelist), the JS submit fails. I normally work around this by temporarily allowing scripts, or by submitting it using JavaScript from the location bar.
However, if you're like me, and you use eSPACE, have NoScript, and not have eSPACE on your whitelist, you'll quickly realise that the UI doesn't just use JS, it requires JS. In other words, the latter solution as stated above will be rather useless. There are only 5 accessible links, and one of them is a javascript: pseudo-URI.
The only plausible reason for the designers to use a JS submit is probably client-side verification. (Which, you can view-source and check for yourself.) Which is really useless, considering that the page is less than 10kB, which loads in less than 5 seconds even on dial-up. In other words, since they have to do server-side verification anyway, why not just do it all server-side?
And the multi-level nested tables (for layout) still suck.

0 Comments:
Post a Comment
<< Home