Feature Request: Ability to easily get the full path of the image
See original GitHub issueUnotes cannot easily get file paths to edit local images. It would be useful if the path could be gotten directly from the displayed image.
Current behavior (Unotes v1.4.3)
When I hover the mouse pointer over the displayed image, nothing happens.
Desired behavior (Implementation Plan)
-
Embed the image “. /img/green1.png” into the document
-
When the mouse pointer hovers over the image, a clipboard copy button appears.
-
You can get the full path of the image by button.
This is clipboard data.
file:///c:/User/user1/sample/img/green1.png
Issue Analytics
- State:
- Created a year ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Feature request : ability to upload images and insert them right ...
And here's a screenshot of the widget, just to be clear: we can only see the file name, not the full path on...
Read more >Feature request #12788: Absolute path to images in composer
It would be nice to be able to save the absolute path to the images you use in a composer, and espacially (more...
Read more >Feature Requests: How to Write, Manage and Prioritize them?
Feature requests are a great way to get the community involved in your product and give them a sense of ownership. What happens,...
Read more >Feature Requests - Kadence Blocks
This is a request for the ability to use ACF and MetaBox Group Fields with Dynamic Content. 0 comments. 2 votes. Vote. Post...
Read more >Angular 2 img src in a relative path - Stack Overflow
I am using webpack and have been able to overcome this issue by require ing the image in the component as a variable...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
OK. I will register an issue for upgrading to tui.editor 3.x as a Feature Request. Then I will actually work on it. I think this ticket should be done independently for tui.editor 3.x support.
Updating to 3.x has been on the roadmap so I think if you are able to make it happen that would be great. I haven’t had a chance to try 3.2 yet so I’m not sure how difficult that will be. It might take a bit of extra effort to get the theming to work but I’m not sure. Let me know if you run into difficulties…