proffapt / ferp Goto Github PK

Improve the UI for the extension and make it appealing to eyes along with being descriptive:

• Better interactive buttons
• Logo for the extension
• Tooltip for the checkbox
• Fix the size

• Update the backend
• Reflect those changes here on the extension
• Host the backend on metaKGP

Since the sole purpose of filling those forms is to be able to download the admit card for end-sems. Then after all the forms are filled, download the admit card automatically.

There are a few javascript codes in this repository, have to implement an extension which shows the variant of feedback a user wants and then selects it. After it the extension does rest of the job for the user - might not include filling the captcha ( kudos to you if you can automate it ) - so the user won't need to run the script manually.

Manifest v2 will not be supported in the near future, shifting to v3 will need to modify the codebase to huge extent.

Work is being done in #24

Make changes so that the extension is also supported on chrome and create a separate binary / zip for it.
POA is not decided, neither is clear to me yet.

Final step towards complete automation - Captcha solving automation

For now the user needs to fill captcha manually.

• Implementing this will need to change the code base to large extent, but will be easier as compared to current one.
• Utilising some API will be our first go-to method.

Chrome Manifestv3 has a few bugs, being listed below:

• 'Not Eligible' Error when using ENTER to submit the form instead of button
• Multiple dangling event listeners on button of main ui
• Doesn't work on first click
• All form filling is giving following error
  • Refused to run the JavaScript URL because it violates the following Content Security Policy directive: "script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules' http://localhost:* http://127.0.0.1:*". Either the 'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.
  • Incorrect captcha.. subtracting more than 1

Releases are published on the following platforms:

• Github - (done)
• Mozilla Add-on Store
• Chrome web store

• Currently the textures don't express out
  • Make the rings a bit bigger
  • Add a Dark mode compatible icon
  • Add institutes logo somehow (Can google about IIT KGP easy to get.)

Add a feature to cycle between different text feedbacks (strengths and weaknesses) while keeping the rest of the inputs the same.

• Analyse the feedback form and get object names
• Type-out the code
• Type-out the negative feedback

• Multiple Button Clicks leads to multiple attachment of event handlers
• All form filler is not working

I am working on a Browser Extension for taking the automation to next level.
Checkout the current progress on the branch: extension and any further branch will be named extension-*.

Roadmap in my mind to implement, along with issues being faced:

• Optimize the js, make them as better as I can.
• Implement a bare extension as a proof of concept.
• Buttons for all 3 variants of feedback.
• A checkbox/radio button to ask whether to use this variant for all of the feedbacks, then wait for the user to fill captcha and press submit feedback.. then the extension will automatically select the next course/prof.. fill the form automatically and then user fills captcha and so on..
  • Test handleProf() function.
  • Get the state of checkbox from main.js onto *_feedback.js
  • Handle the bug when the code doesn't wait for pressing the submit button when the last prof's feedback is filled.
  • Some history or dangling listeners issue, breaks the code if it's not reloaded.
    FIX: reload page and the execute the driver code, maybe?
  • Combine all three scripts into one. Was being done in extension-makeonejs
    • Issue: feedback doesn't change unless you reload. Below is the working fix, will implement later.
      
    • Fix issue: Garbage value of feedback after first iteration
      • Dangling Listeners.
• Complete a full fledged working prototype of feedback form.
• Implement the process to auto-click the alert button - bypassed it, lol.
• Fix the garbage value bug on consecutive forms.

NOTE: These changes were done to dummy feedback form, update these

• In feedback.js - implement document.getElementById('myframe').contentDocument.getElementById('sub'); in-place of anything document.*.

Adding a simple button, most probably in the footer which redirects to the feedback form.

• Chrome
• Firefox - #29

Currently the user is forced to scroll to see the UI.