Releases: GooglyBlox/ClipboardToFileInput
ClipboardToFileInput v3.1
ClipboardToFileInput v3.0
Version 3.0: Complete and total revamp of the extension!
This is a highly recommended update.
Notable changes:
- The single most exciting part is that I've finally been able to resolve #4's issue with disconnected file inputs (and subsequently, the disconnected input in #13). Both of these inputs should work.
- Entirely revamped the extension, cutting ~250 lines of code out and using a slightly different method of injecting the script into webpages (notably for iframes and disconnected file inputs). The code is also much cleaner, and all unused code has been removed.
- Entirely redid how I identify file inputs. In theory, it should be extremely reliable and less case/DOM-dependent.
This is what I would consider a beta version. It hasn't been extensively tested on many websites. It has only been tested on websites that have been previously known to not work, from various issues in the past (ie. #1, #6, #8, #12). If you encounter an issue or a website it doesn't work on, please open an issue!
There is also a known regression (from #11 and #13), in which the "quick-paste" feature no longer works. I couldn't quite find a way to work it into this release, but it'll be re-added in the next one.
Full Changelog: v2.9...3.0
ClipboardToFileInput v2.9-1
Version 2.9-1: Minor Update, reserved specifically to fix #12
As a notice for privacy purposes, the extension now uses the all_frames
flag when injecting content.js
into webpages.
Full Changelog: v2.9...v2.9-1
ClipboardToFileInput v2.9
Version 2.9: Implement #11, update extension popup/icon
The v2.9 update implements #11, by adding a new feature that allows you to quickly paste into file inputs on your screen simply by pressing Ctrl + V (Command + V on MacOS) on a page that has a file input.
It'll initiate a pop-up that asks if you want to enable the feature on that page - whatever your choice is, it'll remember! If you want to reset your preference for the page, you can do so by clicking the extension's icon in your extension bar and resetting your preferences via the popup.
Additionally, I re-did the extension popup/icon. The extension popup now has the GitHub page attached to it, which used to be located in the extension's description.
Full Changelog: v2.8...v2.9
ClipboardToFileInput v2.8
Version 2.8: Fix #10
The v2.8 update resolves #10, by opting to use chrome.windows.create
rather than chrome.tabs.create
. Personally, I think it provides a better and cleaner user experience in general as well!
Full Changelog: v2.7...v2.8
ClipboardToFileInput v2.7
Version 2.7: Fix #9
The v2.7 update fixed #9 as well as an underlying issue in which you may not be redirected to your origin tab.
Full Changelog: v2.6...v2.7
ClipboardToFileInput v2.6
Version 2.6: Code cleanup, bug fixes
The v2.6 update introduces a variety of code cleanups in preparation for a massive overhaul to be released on the Chrome Webstore. Additionally, fixes #8 in which webp/avif files wouldn't upload, and an unnoticed issue in which having text in your clipboard when triggering a file input would hang the clipboard helper.
Full Changelog: v2.5...v2.6
ClipboardToFileInput v2.5
Version 2.5: Code cleanup, new UI, potential bug fixes
The v2.5 update introduces a variety of code cleanups in preparation for a massive overhaul to be released on the Chrome Webstore. Additionally, has a new UI for the overlay.
Edit v2.5 Hotfix 1: Should, in theory, fix #6.
Full Changelog: v2.4...v2.5
ClipboardToFileInput v2.4
Version 2.4: Major Code Cleanup
The v2.4 update introduces a variety of code cleanups in preparation for a massive overhaul to be released on the Chrome Webstore. Additionally, fixes #6 and possibly many other potential edge cases in which the file isn't being uploaded correctly.
Full Changelog: v2.3...v2.4
ClipboardToFileInput v2.3
Version 2.3: Clipboard Security
Since the v2.0 rewrite fixed all of the bugs I've found in my testing, I've decided to dedicate future versions to QoL updates I think would be beneficial. However, 2.3 is a heavily recommended update.
The v2.3 update introduces extra clipboard security, by having a designated clipboard helper page built into the extension, so users will no longer need to manually give clipboard permissions to every webpage, they'll only have to do it once. This should also clear up any security concerns brought up by this issue.
Full Changelog: v2.2...v2.3