Closed Harvester62 closed 1 year ago
Has anybody looked into this issue? Tooltips are important for the usability of the program.
Hi @ClashSAN , sorry to bother you but I think this is an important feature not currently working properly, and @AUTOMATIC1111 is probably not aware of it or too busy. I think the mouse over tooltips should be restored as soon as possible also because it's making my translation work harder, not knowing what tooltips messages are currently to be maintained and translated and what should I remove from the localization file. Perhaps, the policy for tooltips has been changed recently, and I am not aware of it, so I would appreciate very much to receive some feedback about this matter. Nonetheless, I will continue to do my translation work on the Web UI, Scripts and Extensions. Thank you for your consideration and attention. Best regards.
I was able to fix my tooltips. I found that it was an extension that broke them. I don't have a lot of extensions installed so it is possible that other extensions could break tooltips but the one that I found that broke it was Prompt Generator.
I have already submitted an issue here
Thank you @LizardMods , I read your bug report in the other repository and I will check your discovery in my local installation. It seems that what you found might be effectively the source of the issue, looking at the extension's code.
I made a search for any hints.js file inside my \extensions folder and I found the following extensions:
Possibly, also the gif2gif extension might be a source of this issue, given its content very similar to the hints.js of Prompt Generator. The other two extensions have adopted a different approach, with both the file naming and the content itself. I am not a programmer but this seems easily fixable by their respective developers, hopefully.
I have created a PR on both Prompt Generator and gif2gif repositories. The solution was to rename the hints.js file and correct the code inside. I tested them in my local installation and finally I can view all the tooltips! As soon as the two authors will accept the PRs I think I can then close this bug report.
This is also my first contribution as a "coder" to fix a problem, quite easy to be honest.
My above two PRs have been accepted and merged, therefore I am closing this bug report.
Happy to have given my small contribution also by coding a little.
just to add to this sd-webui-controlnet broke tooltips and was fixed with recents commit updates: https://github.com/Mikubill/sd-webui-controlnet/commit/6f394dfd183eb5abc504ef49b4f7b52ffa9f41f8
I haven't yet updated ControlNet to v1.1, still using v1.0 which doesn't have its own \javascript\hints.js file. So, I cannot tell if this is now creating the same identical problem of the two other extensions, but looking inside the sd-webui-controlnet/javascript/ directory there is a file named hints.js
which for sure overrides the current one by A1111, exactly as it happened for the other two extensions I fixed.
If this is the case, then I would recommend the developer to rename and modify accordingly the hints.js file in ControlNet (look at the fix I made for the other extension as a template), and the problem should then be fixed.
Is there an existing issue for this?
What happened?
When hovering the mouse to an option that previously had a tooltip doesn't display the related tooltip. This happens everywhere in the SD Web UI.
Steps to reproduce the problem
Hover the mouse over an item in the UI that has a tooltip associated, like for example Batch or Batch Size (but this happens with any others too), and nothing pops up.
What should have happened?
The associated tooltip to be displayed on mouse hovering.
Commit where the problem happens
3e0f9a75438fa815429b5530261bcf7d80f3f101
What platforms do you use to access the UI ?
Windows
What browsers do you use to access the UI ?
Mozilla Firefox
Command Line Arguments
List of extensions
As a translator, I do have the majority of Scripts and Extensions installed. Here is a screenshot:
Console logs
Additional information
Since this happened before (#5860) and the problem was a missing comma in the file hints.js, I checked it but it seems fine to me.