add Improved Image Support

[Metacor]

fix #37 - added support for local image files opened in the browser

changed ['*://*/*'] to ['<all_urls>']
added chrome.webRequest.onCompleted : for file:// scheme

fix #19 - added the option to use imgur or imgbb (suggestion 2)

suggestion 1 was to add Hover Zoom, which doesn't seem feasible.
suggestions 3, 4, and 5 were already implemented in v1.0.4

close #36 - answered their question

fix cursor hover/selected values - to make interactive elements more easily identifiable.

•   Main Image: grab when hovering ; grabbing when :active

  I also increased the visual selector area to match the actual selector area.
  Everything above the toolbar was selectable, but only the img area visually changed the cursor

•   Custom Modifiers: pointer
•   Custom Keys: pointer when hovering ; text when :focus-visible
•   Zoom Ratio: pointer when hovering ; text when :focus-visible
•   Default Theme, Toast position, and Toolbar Position: pointer

also not sure why, but editing 'css/viewer.min.css' seemed to update thousands of lines in all.js/.css.
nothing changed, and the actual code was only 15 lines of .css, and 0 lines of .js

[Ademking]

@Metacor Thank you so much for your contribution ❤️ We appreciate all the time and effort you’ve put in helping us get to where we are today.

Everything is LGTM.. But, I have some problems with local image files #37 :

• I can't edit images using "Photo Editor"

• Color picker is not working

• Image details also not working

• Print Image, Reverse Image Search and QR Scanning are not working

---

I want to ask you:

• Do you want to merge this pull request and we fix it later in the next version ?
• Wait until we fix those problems and then merge it ?

Thank you again for your contribution @Metacor ! You're the best🥇

[Metacor]

@Ademking I would say to just merge the pull request since it doesn't seem to break anything, but in the changelog specify state "added rudimentary Local File Support" or something similar so people know that it's kinda broken.

• Photo Editor, Color Picker, and Image Details: The CORS policy: Cross origin request doesn't allow access to the file:// scheme
• Upload, Print, Reverse Search, and QR Scanning: Fails to execute 'toDataURL' because local files 'Taint' the canvas

For the above reasons, I'm unsure if these issues can ever be fixed -- local files will likely only ever have access to the base viewer (view, zoom, reset, fullscreen, flip, crop, and extract text).

I believe the base functionality is enough to justify adding Local File support, (being able to zoom in as far as I want is the main reason I use this extension), if you disagree, then I'm not sure if there is any way to salvage Local Files without uploading them as soon as they are loaded (which seems sketchy, and kinda defeats the purpose of it being local in the first place).

If we plan on keeping Local File support, then the best option is to probably add a 'isLocalFile' check before rendering the affected buttons, and just hide them on local files. (I'm having trouble getting this to work, if we go this route I would need help)

Online files seem to be unaffected, (as we would expect, since the 'file://' scheme is on a separate Listener)

[Ademking]

@Ademking I would say to just merge the pull request since it doesn't seem to break anything, but in the changelog specify state "added rudimentary Local File Support" or something similar so people know that it's kinda broken.

• Photo Editor, Color Picker, and Image Details: The CORS policy: Cross origin request doesn't allow access to the file:// scheme
• Upload, Print, Reverse Search, and QR Scanning: Fails to execute 'toDataURL' because local files 'Taint' the canvas

For the above reasons, I'm unsure if these issues can ever be fixed -- local files will likely only ever have access to the base viewer (view, zoom, reset, fullscreen, flip, crop, and extract text).

I believe the base functionality is enough to justify adding Local File support, (being able to zoom in as far as I want is the main reason I use this extension), if you disagree, then I'm not sure if there is any way to salvage Local Files without uploading them as soon as they are loaded (which seems sketchy, and kinda defeats the purpose of it being local in the first place).

If we plan on keeping Local File support, then the best option is to probably add a 'isLocalFile' check before rendering the affected buttons, and just hide them on local files. (I'm having trouble getting this to work, if we go this route I would need help)

Online files seem to be unaffected, (as we would expect, since the 'file://' scheme is on a separate Listener)

Sounds good to me 👍 Again.. I can't thank you enough.

[DevOdian]

Works like a charm. Please do a new release when you have time, @Ademking