Closed Bug 1684428 Opened 4 years ago Closed 4 years ago

Alt Text (Mouseover Popup) is Truncated

Categories

(Core :: Widget: Cocoa, defect)

Product:
Core
Component:
Widget: Cocoa
Version:
Firefox 84
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1592206

People

(Reporter: owencruise1, Unassigned)

Details

Attachments

(3 files)

Screen Shot 2020-12-28 at 11.23.07 PM.png
12.78 KB, image/png
Details
Truncated alt text on 2k display
435.91 KB, image/png
Details
Truncated alt text on 4k display
1.38 MB, image/png
Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:84.0) Gecko/20100101 Firefox/84.0

Steps to reproduce:

Hovered mouse cursor over an xkcd comic to see alt text

Actual results:

Alt text was truncated

Expected results:

Full text should have been shown

Hi,

I wasn't able to reproduce the issue. The alt text is not truncated on my end, neither on Firefox 84.0.1 or Firefox Nightly 86.0a1.

Could you check if this issue also occurs in safe-mode? Here is a link that can help:
https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode#w_how-to-start-firefox-in-safe-mode

Thanks!

Flags: needinfo?(owencruise1)

Can confirm, Firefox 84 under MacOS.
But this only happens on my secondary screen. Firebox windows on the main screen are fine.
Moving the window that is truncating tooltips to the main screen also stops that behavior, and it comes back as soon as the window is on the external screen again.

@Peter and @ahlers --

Sorry for the delay.

I restarted Firefox in Safe Mode and the issue still happens: alt text is still truncated.

I'm also experiencing the same thing that @ahlers mentioned: I'm using two external monitors in addition to my MacBook Pro's built-in screen. The full alt text is displayed (no truncation) on my built-in laptop screen and on my first external monitor. But on my second external monitor the alt text continues to be truncated, whether I'm in Safe Mode or regular mode.

In case it's relevant, the first external monitor (no truncation happens) is connected via DisplayPort whereas the second external monitor (truncation happens) is connected via HDMI.

-- Owen

Flags: needinfo?(owencruise1)
Status: UNCONFIRMED → NEW
Component: Untriaged → Layout: Images, Video, and HTML Frames
Ever confirmed: true
Product: Firefox → Core

More bug details:

The behaviour is persistent on multi-line hover text.
On single-line hover text, it is weirder:
On the first mouseover, the text is truncated as reporter showed. On a second mouseover, the full text is shown.
Example for single-line text: https://xkcd.com/2400/
Example for multi-line text: https://xkcd.com/2401/

More details on my system:
External monitor to MacBook is attached with USB-C.

Component: Layout: Images, Video, and HTML Frames → Widget: Cocoa

Likely a dup of bug 1664670.

(In reply to Timothy Nikkel (:tnikkel) from comment #5)

Likely a dup of bug 1664670.

Yes, or a dupe of bug 1592206 that existed prior to the landing of bug 1592416, which caused bug 1664670.

Could you run mozregression[1] to see when this started happening? If you have never run mozregression before, simply run these three commands in a Terminal window:

sudo easy_install pip
sudo python3 -m pip install -U mozregression --ignore-installed
mozregression --good 2017-01-01

A number of Firefox versions will open in succession to narrow down when this started occurring. Simply type "good" or "bad" in Terminal based on whether or not a build reproduces the bug. Once finished, please post the output from the last run. It should give a last good and first bad revision as well as a link to look at the changesets in that range. Thank you!

[1] https://mozilla.github.io/mozregression/

Flags: needinfo?(owencruise1)

(In reply to Stephen A Pohl [:spohl] from comment #6)

(In reply to Timothy Nikkel (:tnikkel) from comment #5)

Likely a dup of bug 1664670.

Yes, or a dupe of bug 1592206 that existed prior to the landing of bug 1592416, which caused bug 1664670.

Yes. The reason I think it is bug 1664670 is because this bug only happens on the users external screen.

Flags: needinfo?(owencruise1)

Hi Stephen,

Not really sure what you're asking me to install. I'm extremely hesitant to click on any dmg links just because somebody posted them on a forum even if they have "mozilla.com" in the URL. I don't know what a "try build" is.

I'm not a developer, I just thought this was a way to report bugs to Mozilla so they would be fixed in the next browser update version. I sent this in the same way I'd file a report at apple.com/feedback if I had a bug report for one of their applications.

  • Owen
Flags: needinfo?(owencruise1)

(In reply to owencruise1 from comment #9)

Hi Stephen,

Not really sure what you're asking me to install. I'm extremely hesitant to click on any dmg links just because somebody posted them on a forum even if they have "mozilla.com" in the URL. I don't know what a "try build" is.

I'm not a developer, I just thought this was a way to report bugs to Mozilla so they would be fixed in the next browser update version. I sent this in the same way I'd file a report at apple.com/feedback if I had a bug report for one of their applications.

  • Owen

Hi Owen, no worries at all. Try builds are test builds, built on the Mozilla infrastructure, to check potential code changes. Sometimes, as in this case, when a developer like myself is unable to reproduce a problem, we may suggest code changes based on best guesses and then ask reporters to see if the bug is fixed for them in a test build (try build) with those code changes applied. I have asked Timothy to do the same in bug 1664670 comment 2, with the exact same builds. I asked you to test these builds to see if your bug is a duplicate of bug 1664670 in case you were unable to reproduce the problem anymore in my try builds, or if it is rather a duplicate of bug 1592206 which I do not expect to be fixed in my try builds.

You could confirm my identity via https://people.mozilla.org/p/spohl, but I certainly understand your hesitancy to download and install binaries from sources that aren't known to you. If you would rather not try these builds I will just make a note for myself to ask you to retest once my code changes have made it into an official build, not just into one of our test builds.

Thanks Stephen for understanding and for providing more information. I'll hold off on trying the test builds, and instead if you'd like I can just let you know if the bug is fixed in the next released official version of Firefox.

If it's at all relevant, the USB-C monitor (where truncation is not happening) is at 3840x2160 60 Hz and the HDMI monitor (where truncation is happening) is at 2560x1440 60 Hz.

Hi Owen, the fix for bug 1664670 is now in the official Firefox Nightly build. Could you check if you can still reproduce this with the latest Nightly build? You can download it from https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly. Make sure to click on the download button next to the Nightly channel. Thanks!

Flags: needinfo?(owencruise1)

Hi Stephen,

I downloaded Firefox Nightly and tried it out.

Interestingly, now the alt text is truncated on both of my external monitors (the 2k one and also the 4k one). The alt text appears just fine on my built-in monitor.

I've attached screenshots showing what I mean.

-- Owen

Flags: needinfo?(owencruise1)

Also, this is on Firefox Nightly 86.0a1, macOS 11.1.

The xkcd issue is probably a dupe of bug 1592206.

Thank you for letting us know. Closing as duplicate of bug 1592206.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: