![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
randomlingSo I'm working on Bug 2886, and for most of it I have a working patch. (Back end, at least - and the front end looks like it will be fairly easy.)
I have one question on the spec here, which I wanted to open out to the wider community.
We're allowing title attributes (ie: hover text) for the user-defined links that show up in the sidebar. Showing them on links was, once I had much hand-holding through the codebase and figuring out what in hell I was doing, not that hard. However - that particular widget also allows users to define headings (by simply plugging in a title and no link).
It turns out it's a much harder problem to figure out how to allow hover text over the headings without breaking everything else, 'cause that refers to the way all the headings for the modules are printed, and hover text is (on most of them) an attribute that will never get used. So it's going to end up with passing a lot of empty strings back to the appropriate function, if I implement this.
So my question is: should I implement the possibility of hover text over headings? What do you guys think? Is that worth the time and effort and rejigging of the codebase to allow it?
It might perhaps be useful to have such an attribute available, should we decide to make more hover-text-related changes in the future.
Anyway - please let me know your thoughts.
(Also, I'm feeling anxious that I have been confusing or unclear. Do let me know if there's anything you need me to clarify or explain further.)
I have one question on the spec here, which I wanted to open out to the wider community.
We're allowing title attributes (ie: hover text) for the user-defined links that show up in the sidebar. Showing them on links was, once I had much hand-holding through the codebase and figuring out what in hell I was doing, not that hard. However - that particular widget also allows users to define headings (by simply plugging in a title and no link).
It turns out it's a much harder problem to figure out how to allow hover text over the headings without breaking everything else, 'cause that refers to the way all the headings for the modules are printed, and hover text is (on most of them) an attribute that will never get used. So it's going to end up with passing a lot of empty strings back to the appropriate function, if I implement this.
So my question is: should I implement the possibility of hover text over headings? What do you guys think? Is that worth the time and effort and rejigging of the codebase to allow it?
It might perhaps be useful to have such an attribute available, should we decide to make more hover-text-related changes in the future.
Anyway - please let me know your thoughts.
(Also, I'm feeling anxious that I have been confusing or unclear. Do let me know if there's anything you need me to clarify or explain further.)