Closed Bug 1906348 Opened 1 year ago Closed 1 month ago

google.com News search on Firefox for Android: news titles contain extra linebreaks

Categories

(Web Compatibility :: Site Reports, defect, P2)

All
Android

Tracking

(Webcompat Priority:P2, Webcompat Score:6, firefox147 verified)

VERIFIED FIXED
Webcompat Priority P2
Webcompat Score 6
Tracking Status
firefox147 --- verified

People

(Reporter: mstange, Unassigned)

References

()

Details

(Keywords: webcompat:contact-complete, webcompat:site-report, Whiteboard: [webcompat:sightline][webcompat:japan])

User Story

platform:android
impact:annoyance
configuration:general
affects:all
branch:release
user-impact-score:300

Attachments

(2 files)

Attached image screenshot

This was originally reported in https://www.reddit.com/r/firefox/comments/1dukx2t/another_reason_why_google_is_evil/ and I can reproduce it.

Steps to reproduce:

  1. In Firefox Nightly for Android, do a google search for the string "android".
  2. Switch to the "News" tab.

Expected results:
The titles of the news in the top list should have reasonable line breaks.

Actual results:
In each result, there's a line break after the first word and second word of the title.

Chrome:

You could get a cut of Google's
$700 million lawsuit payout if you
own an Android

Firefox:

You
could
get a cut of Google's $700 milli...

Looking at the DOM of the page in the devtools inspector, there is a <br> after "You" and after "could".

Add a ni for Dennis to reach out to Google

Severity: -- → S4
User Story: (updated)
Flags: needinfo?(dschubert)
Priority: -- → P2

These <br> tags aren't there in Chrome, so this isn't a rendering difference or anything. I've reached out to them.

Flags: needinfo?(dschubert)

It doesn't look like we need to do any diagnosis here, so removing that flag for now.

Whiteboard: [webcompat:sightline]
Duplicate of this bug: 1938058

As one additional data-point: you can see this bug reproducing in the Firefox screenshots on https://github.com/webcompat/web-bugs/issues/141292 (though that particular github issue was focused on something else -- an unexpected left-vs-right ordering of text & images that the reporter was seeing -- and that issue was closed because that part wasn't reproducible).

(In reply to Dennis Schubert [:denschub][OOO - back Jan 7th] from comment #3)

I've reached out to them.

I'm not sure we ever heard back from this outreach, so I followed up on the email thread today.

The severity field for this bug is set to S4. However, the following bug duplicate has higher severity:

:ksenia, could you consider increasing the severity of this bug to S3?

For more information, please visit BugBot documentation.

Flags: needinfo?(kberezina)
Severity: S4 → S3
Flags: needinfo?(kberezina)
Webcompat Priority: --- → P2
Duplicate of this bug: 1944209
Webcompat Score: --- → 6
Whiteboard: [webcompat:sightline] → [webcompat:sightline][webcompat:japan]
User Story: (updated)

As chatted in the webcompat channel, I am removing the keyword from webcompat:site-wait. Keeping webcompat:contact-in-progress should be enough.

User Story: (updated)

I have filed b/467804205 to track this within Google.

We believe we've identified the root cause and will be deploying a fix soon.

This should now be fixed, please verify on your end and let us know if you still see any issues.

Yes, this looks fixed on my end. Thank you!

Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED

Verified, the issue no longer reproduces.

Tested with:

  • Browser / Version: Fenix 147.0-candidate build 1
  • Operating System: Google Pixel 5 (Android 14)
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: