3 ms·
Potentially only, where i work, browsers are managed by IT, no way to patch stuff, no devtools. Also depending on the design, adding your code may never work un
by agumonkey 5y ago
Potentially only, where i work, browsers are managed by IT, no way to patch stuff, no devtools. Also depending on the design, adding your code may never work unless you reverse the whole codebase (the app in place is extremely stateful, all a.href are replaced by procedural js calls).
Don't laugh but I had more results scripting mouse/keyboard automation on 90s oracle GUIs [0] than the app I mentioned above.
[0] I could prefill half the stuff and help the rest with powershell, it gave me 70% time reduction on most tasks
- CraigJPerry 5y agoAhh that sucks royally. I've been in similar and it's soul sucking! <flippant-comment-from-a-random-hn-poster-who-doesnt-know-your-circumstances> The job market's great right now </flippant-comment-from-a-random-hn-poster-who-doesnt-know-your-circumstances> :-) Hopefully more usefully as a comment - browsers are super hackable, you might be able to use a javascript bookmarklet to effect some improvements. Something like this https://caiorss.github.io/bookmarklet-maker/ https://caiorss.github.io/bookmarklet-maker/ (there are others) makes life easier for creating these.
- agumonkey 5y agoI don't mind the comment above, he's somehow right that html/js is more open to ad-hoc patches than native code. Except when admins forbid you to. bookmarklets don't allow for injections into the app so it wont work