搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

Learn More

FF version 23.0 - The title attribute not longer renders a tooltip for images.

  • 6 个回答
  • 14 人有此问题
  • 4 次查看
  • 最后回复者为 cor-el

more options

Since version 22.0 and now 23.0 none of the title attributes work for images or anchor tags as far as displaying tool-tips to the user. The QA department just doesn't accept, "Well, it's there.", as an appropriate fix to bugs.

Since version 22.0 and now 23.0 none of the title attributes work for images or anchor tags as far as displaying tool-tips to the user. The QA department just doesn't accept, "Well, it's there.", as an appropriate fix to bugs.

所有回复 (6)

more options

Can you post a link to a publicly accessible page that doesn't require authentication (signing on)?

Start Firefox in Safe Mode to check if one of the extensions (Firefox/Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Firefox/Tools > Add-ons > Appearance).

  • Do NOT click the Reset button on the Safe Mode start window.
more options

No I cannot. We are behind a massive firewall. I've tried the Safe Mode trick. Nothing. Thanks for trying to help.

more options

I'm struggling to think of a way to block the title attribute tool tip... two things come to mind, but it's unlikely they are happening accidentally:

(1) Blank child node title will block parent node title. What I mean is:

<a href="blah" title="link title"><span title="">link text</span></a>

(2) Scripts can do it, but probably you would know whether you are doing this...

Example: javascript - How to disable tooltip in the browser with jQuery? - Stack Overflow

Edit: Escaped HTML.

由jscher2000 - Support Volunteer于修改

more options

Can you post a stripped down version of the code that is used and that shows this problem?

more options

Excellent observations both.

I know what you mean in #1. We don't code that way.

We have not written any jQuery that is blocking. The other developers that have upgraded to 22.0 or 23.0 don't have the problem.

more options

Create a new profile as a test to check if your current profile is causing the problems.

See "Creating a profile":

If the new profile works then you can transfer some files from an existing profile to the new profile, but be careful not to copy corrupted files.