Firefox and Internet Explorer both display tooltips for <option> elements if that element has its "title" attribute set. Safari does not. I would like to request that this functionality be added to Safari. Attaching a test case reduction that displays this in both 419.3 as well as the latest nightly. (WebKit-SVN-r16342.dmg Wed Sep 13 12:53:19 GMT 2006)
Created attachment 10541 [details] test case reduction
Using WebKit nightly r27630 (2007-11-09) Example: http://coe.berkeley.edu/news-center/multimedia/video-gallery/dean-shankar-sastry-s-welcome-message -- hover over the emphasised item in the navigation portlet at left hand side. In OmniWeb, Camino and Firefox the tooltip reads "Meet the new Dean of the College of Engineering". In WebKit, a tooltip appears but it simply presents the URL. As so many sites use Plone, you might like to raise priority of this bug. Thanks Graham --- Here's a relevant extract from the source of that page: <div class="contenttype-multimediafeature"> <a href="http://coe.berkeley.edu/news-center/multimedia/video-gallery/dean-shankar-sastry-s-welcome-message" class="state-public navTreeCurrentItem visualIconPadding" title="Meet the new Dean of the College of Engineering">Dean Shankar Sastry's Welcome Message</a> </div> --- title="Meet the new Dean of the College of Engineering" is not rendered.
Confirmed with a local debug build of WebKit r27683 with Safari 3 Public Beta on Tiger. Firefox 2.0.0.9 will display a tooltip (you must click the pop-up box and hover over the item in the list before it appears).
I am not able to reproduce this issue in Safari Technology Preview 152 using attached test case and also test case from Comment 02 turned into JSFiddle: Link - https://jsfiddle.net/s2pf9w1L/ In attached test case, upon opening drop-down, if I leave my cursor for few seconds on option, it shows "option tooltip" and it is same across all browsers (Chrome Canary 107 and Firefox Nightly 106). In case of JSFiddle, it also show "Meet New Dean" as tooltip, if I leave cursor on the link. I think it is working as intended and I am going to mark this as "RESOLVED CONFIGURATION CHANGED". If it is not fixed or still an issue, please reopen. I will tag few other Webkit Engineers to confirm my analysis as well.