Closed (outdated)
Project:
Glossary
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
23 May 2012 at 10:03 UTC
Updated:
1 May 2017 at 17:19 UTC
Jump to comment: Most recent
Comments
Comment #1
nancydruI think that would be a question for that module.
Comment #2
Dave Cohen commentedA hovertip is not its own frame, so no scrollbars. You should be able to tweak it's width with CSS. Is the width the problem?
Comment #3
jvieille commentedThe problem is that the text in hovertip might be muche longer than the allowed size, even if the hovertip reaches the full screen.
I would expect a "Read more..." link within the hovertip to reach the full description in a frame.
Comment #4
Dave Cohen commentedI'm not sure how glossary generates the hovertip markup. Sounds like you want a change to that code.
Comment #5
jvieille commentedNancy, what do you think?
Comment #6
nancydruWell, I guess I'll have to see if this has changed since I originally implemented it according to the Hovertips documentation.
But, I must say this: the intent of Glossary is to have a small-ish definition shown. If your hovertip is that big, you might want to re-examine using Glossary for this.
Comment #7
jvieille commentedI think the use case makes sense:
- the hovertip gives "tips" about the glossary item, that's really OK.
- However, it would be great to have a handy mean to reach the full description from here, being either the term description or an associated node i.e. "taxonomy node".
This would look like a feature request by now.
Comment #8
nancydru